The 6.x release of StreamBase includes significant improvements for developer productivity. Follow these steps to insure a smooth transition to the new release.
-
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. -
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 → 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 → and click in the confirmation dialog.
-
Do the same for the SB Test/Debug perspective.
-
-
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.
-
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.
-
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 the entry for SB-11437 in the 6.0.1 Release Notes.
The current release of StreamBase includes significant changes compared to release 3.x. Many of the differences are transparent, but some will change how you use StreamBase.
If you have existing work in StreamBase Studio 3.x that you want to bring over to the current release, you must perform some migration steps after installation:
-
Read Differences Between 3.x and 5.x to understand in what ways the StreamBase authoring environment has changed.
-
When you are ready to perform your project migration, follow the steps in Migrating Studio 3.x Projects.
-
When you're finished importing, read After Migrating a Project, which lists the changes to be aware of in your migrated project.
-
If you have custom Java operators or adapters, follow the additional steps in Special Case: Migrating Java Projects.