Editing LiveView Run Configurations

A configuration name is generated for you when you first run a fragment. You can change the name according to your site's standards. The name you enter is not reflected in the navigator pane on the left until you click Apply.

Specify the path to the LiveView project to be run. Paths are measured from the root of the current Studio workspace. The easiest way to enter the correct path format is to browse for a project using the Browse button. The resulting dialog shows a list of all projects in your workspace. Select the LiveView project of interest and click OK.

Specifies the Client API listening port for this EventFlow engine. Choose one of the following options:

Use this control to specify the API listening port for the LiveView server run with this LiveView project. The options are used as described for the StreamBase engine port above, except that the default port is 10080.

Specify which configuration files to use in the next run or debug launch of this EventFlow project. By default, all configuration files in src/main/configurations are selected. If your project contains more than one configuration file of the same HOCON type, specify only one per type. For example, if your project experimentally contains two configuration files of type ldmengine, the launch halts with a runtime error. Select which configuration file to use for the next launch from Studio.

The default cluster name for Studio-initiated nodes is the system login name in effect when Studio started, and is not specified in a Run Configuration. You can change the default cluster name in Studio Preferences.

Alternatively, you can specify a cluster name on a per-run configuration basis in the Use name field.

This field specifies a name for the node that Studio creates to contain this fragment. This field uses a pattern of variables as described for the EventFlow Run Configuration.

Use this table to specify parameters for Studio to use when it installs a node to contain this fragment. See the description of the same field in the EventFlow Run Configuration.

Remember that all LiveView fragments are launched into StreamBase Runtime nodes, and that nodes are always part of a StreamBase Runtime cluster.

Studio enables the Append environment to operating system environment setting by default. This means the shell environment for the operating system in which Studio runs is passed to and available to fragments running in nodes. Any variables specified in this tab can supplement the system settings, or can modify or override existing system environment variables.

You can select the Use specified environment only control to restrict the launched node's environment settings to those specified in this tab.

A StreamBase Runtime node has its environment set at node installation time. This has the following consequences:

The New/Edit Environment Variable dialog contains a Variables button, which is a feature inherited from Eclipse. Use this button to specify the value of an environment variable using one or more Eclipse system variables whose contents are resolved by Eclipse when this configuration is run. Use the Help button on this dialog for further information on each available variable.

The list of variables includes ${sb_home}, which is defined as the absolute file system path of the StreamBase installation directory as currently set in Studio's Preferences dialog.

See Environment Variables for a further discussion of the ways environment variables are used in StreamBase.

Fragment launches in Studio cannot set customized values for the TIBCO_EP_HOME or JAVA_HOME environment variables because those have particular meaning for Studio operations. This is true even if these variables are inherited from the system environment.

Studio detects and blocks attempts to use these two variables, whether explicitly specified in this Environment tab, or inherited from the system environment. In this case, Studio displays a warning dialog like the following.

Select the Remember my decision check box to suppress this warning dialog for future fragment launches.

This option determines where this run configuration is saved. The default setting, Local file, saves configurations in the workspace metadata area. As an alternative, you can select Shared file to save this run configuration as a file in one of your project folders. In this case, the run configuration is saved as Name.launch, where Name is specified in the Name field. Specify the target project folder using the Browse button.

The favorites menu is a list of run configuration names that appears in the second section of the drop-down menu of the Run and Debug buttons on the toolbar. The first section contains a changing list of recently Run Configurations. Add a configuration to the favorites section to keep it in the menu, even when other applications have replaced it in the recently-run section. This option performs the same function as the Organize Favorites option in the Run and Debug drop-down menus.

Use this section to specify a non-default character encoding for log messages sent to the Console View (and optionally to a standard output file).

Allocate Console is selected by default. This specifies using the Console view to display logging messages written to standard output and standard error.

Input File is not supported by LiveView fragment launches.

Output File is unselected by default. To specify that standard output and standard error of your fragment's run are written to a log file, select the Output File check box, and enter a path to a file. If the specified file does not exist, it is created for you. If both Allocate Console and Output File options are selected, log messages are written to both places. You must designate the path to the file using Eclipse-specific syntax. Rather than typing a path, use the Workspace or File System buttons to navigate to a workspace or file system folder, and specify a file name. These buttons let Eclipse write the syntax for you. If you are familiar with the Eclipse syntax required in this field, you can use the Variables button to build up a path from components.

Append is dimmed unless the Output File option is selected. Select the Append check box to have log messages appended to the file specified in the Output File field. If unselected (the default setting), the designated file is overwritten with each run of this configuration.

Use this option to specify that the launching process itself runs in the background. (The LiveView server is always run in the background.) Selecting this box returns control to Studio immediately when you launch this configuration, without displaying the usual Starting Server dialogs.