Editing StreamBase Application Run Configurations

A configuration name is generated for you when you first run a StreamBase application. 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 application archive file to be run or debugged, using the Browse button. The resulting dialog shows the folder path to all StreamBase applications in your Studio workspace. Select the archive of interest and click OK.

Specify which configuration files to use in the next run or debug launch of this StreamBase application, using the Browse button. If your application contains more than one configuration file of the same HOCON type, specify only one per type. For example, if your application experimentally contains two configuration files of type sbengine, 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 StreamBase application. For example, you can specify here the same node name you are using in your test and deployment environment with the epadmin command.

Studio's default node name is generated from a naming pattern generated from a set of variables. Use the Node Name Variables button to select a different set of project-related variables, or use the Other Variables button to specify variables available to Studio as a whole. The naming pattern you assign must include the S(SeqNum) variable, to make sure that a sequence number is assigned to make node names unique.

Use this control to specify one or more parameters for Studio to use when it installs a node to contain this StreamBase application. The valid parameters are the same as can be used with the epadmin install node command; run epadmin help node at the command prompt to see the available parameters.

The feature is best used with parameters such as memorysize to specify a JVM heap size larger than the default 512 MB for certain EventFlow or LiveView fragments.

Use this field to define substitution variables, or to specify a file that contains substitution variables. See Substitution Variables for more information on using substitution variables in configuration files.

Take, for example, a security configuration file that includes the property portNumber = ${LDAP_PORT}. If you include a Name-Value pair in the Substitutions table, where the name is LDAP_PORT and the value is a non-default port such as 5389, then when the project is run and the configuration file is read, the portNumber = line in that security configuration file is read as if the file contains: portNumber = 5389.

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 dropdown 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 StreamBase application launches.

Output File is unselected by default. To specify that standard output and standard error of your application'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 checkbox 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 StreamBase server that hosts your StreamBase application 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.