How to improve the BusinessWorks Studio user experience
While working on large workspaces with Studio this is relatively common to face some slowdowns and even sometimes some freezes.
Because of different factors, like limitations in the underlying Eclipse layer and possible side effects of anti-virus software’s commonly used on Windows workstations, this cannot be fully resolved but there are a number of things that can be done to limit slowdowns.
This article goal is to explain what can be done both in the BusinessWorks Studio configuration and best practices to apply while using it to limit slowdowns.
If you know other options please let me know and I will add them in this article.
# BusinessWorks Studio configuration improvement
There are two things to do to improve Studio behavior:
. Use a modern non-blocking Garbage Collector
. Increase the Java Max Heap Size to 4GB (note that this is the default value in recent BusinessWorks versions)
This can be done with the following:
. Go to the <TIBCO_HOME>/studio/4.0/eclipse directory
. Edit the BusinessStudio.ini file with the following:
— Update the following line
-XX:+UseParallelGC
with
-XX:+UseG1GC
- Update the following line
-Xmx2048m
with
-Xmx4096m
After editing the BusinessStudio.ini the last lines of the file should look like this:
# BusinessWorks Studio usage best practices
Limiting the number of open projects in the Workspace
When working on a Workspace where you have a significant number of projects a good practice to limit slowdowns is to close the projects you are not working on.
This can be done by selecting the project you want to close, doing a right click and selecting ‘Close Projet’ in the menu option.
The project can be re-opened later with just double clicking on its icon.
Limiting the number of open tabs in Studio
When working on a large project or multiple projects at the same time you may quickly have a significant number of tabs open in Studio. A good practice to limit slowdowns is to limit the number of open tabs.
This can be done by right clicking on one of the open tabs and selecting one of the available ‘Close’ options.
Limiting the validation scope
By default the scope of the validation feature of Studio is the whole workspace. This can be reduced to the selected projects or the selected elements.
This is usually very useful to only see validation problems related to the project, or application, you are working on.
This can be done with the following:
Select the ‘Problems’ tab and click on the ‘Filter’ icon:
The following panel is displayed:
To display only problems for the project, or the application, you are working on check the ‘Errors/Warnings on Project’ option and make sure the scope is set to ‘On elements in selected projects’.
After applying this selection when you select a resource of an application, like a Process or a Schema, the ‘Problems’ tab only displays problems of the selected application.
In the example below you only see the problems of the TestMapping application because the Process ‘Process1’ is selected.
It is possible to do the same at ‘Selection’ level (a package or a specific element, for example a group of Processes from a given package, a Process or a Schema) using the ‘Errors/Warning on Selection’ option and the ‘On selected Element on its children’ scope.
Disabling the automatic Workspace build
It is also possible to temporarily disable the automatic Workspace build, for example while doing changes that impact significantly the project.
This can be done with the following:
. Using the ‘Windows -> Preferences’ option of the main menu, open the ‘Preferences’ panel
. In this panel select the ‘General -> Workspace -> Build’ sub-panel and uncheck the ‘Build automatically’ option
Once changes are completed you can re-enable the automatic build by just checking again the option.
# Additional elements
For additional BusinessWorks Studio tips and tricks you may refer to the following article:
