Migrating From StreamBase 5 to 6

Follow these steps to insure a smooth transition to a 6.x release from a 5.x release.

  1. StreamBase Systems strongly recommends that you reset the perspectives in StreamBase Studio to pick up the new layout that includes newly added Views and Editors. To reset perspectives, follow these steps:

    • [Optional step] If you have a highly customized perspective arrangement, you can save it before resetting the perspective. This allows you to return anytime to your customized layout. Use the Window → Save Perspective As menu to save the current perspective. Do not re-use an existing StreamBase perspective name. For example, save SB Authoring as My SB Authoring.

    • Open the SB Authoring perspective. Invoke Window → Reset Perspective and click OK in the confirmation dialog.

    • Do the same for the SB Test/Debug perspective.

  2. If you open a 5.x workspace with Studio 6.x, the first time you open the SB Test/Debug perspective, you may see an error message stating that the debugTerminalView cannot be found. You can safely ignore this message, which occurs because the Debugger View was removed from Studio 6.x in favor of the new visual debugger facilities.

  3. Your Studio 5.x projects open without error in Studio 6.x, and you can run them and continue to develop them without a migration step.

  4. EventFlow application files from Studio 5.x open in Studio 6.x and are silently upgraded to take advantage of new features such as Named Schemas. You may notice that, on opening an EventFlow file generated in Studio 5.x, it immediately has an asterisk in its name tab, indicating that there are unsaved changes from this silent upgrade. It is safe to save the file and continue working.

  5. If your EventFlow or StreamSQL application uses dynamic variables, there may be an issue when migrating your applications. Previous releases allowed you to use the same name for variables, field names, and stream names. Release 6.0 introduced support for hierarchical tuples, and introduced self-referencing dynamic variables. These features were added at the cost of the possibility of ambiguity in resolving the names of identically named objects. For details on this issue, including workarounds and best practice recommendations, see this release note.