Launching eStudio

To start the Fiorano eStudio application, perform the actions below:

  1. Do one of the following:

    1. Navigate to the Fiorano Tools folder through the Start menu and click Fiorano eStudio.
    2. Navigate to $FIORANO_HOME/eStudio and run the eStudio executable file.

  2. Workspace Selection dialog box is displayed prompting for the workspace directory. Workspace is a directory where repositories (Event Processes, Microservices and other metadata) are stored with the default workspace set to $FIORANO_HOME/runtimedata/eStudio/workspace.


    The Remember workspace option can be selected to save the workspace used to avoid displaying the dialog box when eStudio is launched next time.

    • It is recommended that the default workspace is used.
    • The workspace preferences are stored at FIORANO_HOME/runtimedata/eStudio/

The following preferences are stored in workspace preferences: wsLastUsedWorkspaceswsRemember and wsRootDir.

  • If a user chooses a workspace and selects the Remember Workspace option, this can then be changed by changing the value of wsRemember to false in the workspace preferences.
  • When the Fiorano eStudio has completely launched, a user can switch between different workspaces. The option to switch the workspace is present at File > Switch Workspace.
  • The current workspace selected is shown in the Fiorano eStudio title bar. 
    By default, eStudio is launched in the Offline Event Process Development perspective and the offline repository is populated when eStudio is launched for the first time.
  • If eStudio does not load properly, install XULRunner on the machine. Follow the guide lines from: to install and add the script below to $FIORANO_HOME/eStudio/eStudio.ini and restart eStudio:

  • In the Windows Server 2008, there are certain permissions settings that do not allow standard eclipse to function normally if eStudio is not running as an administrator. To resolve this, run eStudio assigned as an administrator.

32-bit or 64-bit eStudio launchers may be used depending on the JVM used in the system.

Understanding eStudio Views

There are various panels/views in eStudio meant to accomplish various tasks.

Event Process Repository

The Event Process Repository view is one of the views of the Offline Event Process Development perspective.  To display this view, navigate through Window > Show View > Other > Fiorano > Event Process Repository.

Event Process Repository view shows all the event processes created in the Offline Event Process Development perspective, under various categories.

Figure 1: Event Process Repository

Fiorano Orchestration

Offline and Online Event Process Development perspectives are comprised of an editor area called Fiorano Orchestrator. When an Event Process is opened (double-click the Event Process), the design of the event process is shown in the Fiorano Orchestrator where further editing can be done.

Figure 2: Orchestration Editor

Micro Service Palette

The Micro Service Palette shows the microservices that are present in the eStudio repository. It contains all the Fiorano microservices grouped into various categories such as: Bridges, Collaboration, DB, Error, File and so on as shown in the figure below.

To display the Micro Services view, navigate to Window > Show View > Other > Other > Micro Service Palette.

Figure 3: Fiorano Micro Service Palette


The Search option in the Palette enables retrieval of microservices upon typing the microservice name in it.


The Properties view displays all the property names and values for any selected item such as: a microservice instance, route, port, and so on.

To display the Properties view, navigate to Window > Show View > Other > General > Properties.

Placing the cursor on a property displays the property description.

Figure 4: Properties view


To explore the options available in the Properties view, refer to the Common Configurations section.


While working in the Fiorano environment, the errors and warnings that occurr are displayed in the Problems view. For example, when an Event Process containing errors is saved, the errors are displayed in the Problems view.

To display the Problems view, navigate to Window > Show View > Other > General > Problems.

Figure 5: Problems view

By default, the problems are grouped by their severity level. This grouping can be changed using the Group By option in the drop-down menu present at the upper-right part of the Problems panel.

Problems view can also be configured to show the warnings and errors associated with a particular resource or group of resources. This is done using the Configure Contents option in the drop-down menu.

Additionally, you can add multiple filters to the Problems view and enable or disable them as required. Filters can either be additive (any problem that satisfies at least one of the enabled filters will be shown) or exclusive (only problems that satisfy all of the filters will be shown).

Error Log

The Error Log view captures all the warnings and errors logged in the Fiorano environment. The underlying log file (.log) is stored in the .metadata subdirectory of the workspace. The Error Log view is available under Window > Show View > Other > General > Error Log.

Figure 6: Error Log view

Micro Service Repository 

Fiorano eStudio provides a Service Repository view which shows a categorized list of all available microservices. When the Fiorano eStudio is launched for the first time, the offline repository is loaded from the installer.

Microservices which are available only in the Service Repository can be used for composing event processes in eStudio. Microservices can be imported from or exported to a file system or a Fiorano ESB Server from the Service Repository.

To open this view, navigate to Window > Show View > Other > Fiorano > Service Repository.

Figure 7: Micro Service Repository

Project Explorer

The Project Explorer view lists all the projects in eStudio. All the Event Processes, Microservices and Mapper projects are shown in the Project Explorer view.

To use Version Control, corresponding plug-ins have to be added in drop-ins. If the drop-ins are added, then the version control options will be available in the context menu of a project in this view.

To open Project Explorer view, navigate to Window > Show View > Other > General > Project Explorer.

Figure 8: Project Explorer

The microservice projects are shown as closed projects by default. Open a project by right-clicking on a project and by selecting the Open Project option.


To enhance performance, close the microservice projects when they are not being used.


All the views above are available in both Offline and Online Event Process Perspective. The views below are available only in the Online Event Process Perspective.

Server Explorer

The Server Explorer view shows the Enterprise servers, which contains the Event Process Repository and Peer Repository nodes. The Event Process repository is centrally stored in the Enterprise Server. The Enterprise Server provides API access to event processes such as save, view, export, launch, debug, stop, and similar actions as required. The Fiorano eStudio provides an easy-to-use GUI to manage event processes. The Peer Repository shows the peer servers connected to the Enterprise Server.

To open the Server Explorer view, navigate to Window > Show View > Other > Fiorano > Server Explorer.

Figure 9: Server Explorer

Fiorano Debugger View

The Fiorano Debugger view shows the list of routes on which the debugger is enabled and the messages trapped within each route. This enables debugging message.

To open the Fiorano Debugger view, navigate to Window > Show View > Other > Fiorano > Fiorano Debugger.

Figure10: Fiorano Debugger view

Service Descriptor Editor

Microservices can be edited using a Service Descriptor editor.

To edit a microservice in the Service Descriptor editor, right-click the desired microservice in the Micro Service Palette or in the Micro Service Repository and click the Edit option from the context menu.

Attributes of the Service Descriptor are divided into three categories:

  • Overview – Contains general information about the microservice such as Name, GUID, version, and icon.
  • Execution – Contains information about microservice ports, runtime arguments, launch options and log configuration.
  • Deployment – Contains information about microservice resources, dependencies and general deployment information.

Figure 11: Service Descriptor Editor


Changes made to the microservice are saved to the repository only when the editor associated with the microservice is closed after editing.

Adaptavist ThemeBuilder EngineAtlassian Confluence