To open the Online Event Process Development perspective, perform the following steps:

  1. Click Windows on the menu bar, select Open Perspective and click on Others.. option from the drop-down menu. Or click the Open Perspective button from the shortcut bar and select Other... from the drop-down menu. The Open Perspective dialog box appears.
  2. Select the Online Event Process Development to open online perspective. Click the OK button.

Online perspective contains all the views and editors required for online application development. During online Event Process development, event process development can be done after logging into the Enterprise Server.

After switching onto Online Event Process Development mode, select the Enterprise Server node, right-click and select Login to login into the Enterprise Server.

Figure 1: Enterprise Server node

By default the configurations of the Enterprise Server running locally is set on the Enterprise Server node. These can be changed from the properties view if required.

Each time during login, eStudio fetches the information of Services, Event Processes and Peer Servers from the Enterprise Server and populates the online repository. The default location of the online repository for a particular Enterprise Server is $FIORANO_HOME/runtimedata/eStudio/workspace/.repositories/Online/<Enterprise Server name>. Screenshot of the Online Event Process Development mode is shown in Figure 2.

Figure 2: Online Event Process Development perspective

The Event Process Repository node contains a tree structure of various Event Processes in the Enterprise Server.

The Peer Repository node contains the information of Peers connected to the Enterprise Server.

Fiorano Views

All the views described in Offline Event Process Development mode are available in Online mode. There are additional views specific to Online mode. These views are described in this section.

Server Explorer

The Server Explorer view shows the Enterprise servers, which contains Event Process Repository and Peer Repository nodes.

The Server Explorer view is available under Window > Show View > Fiorano > Server Explorer.

The Event Process repository is centrally stored in the Enterprise Server. The Enterprise Server provides API access to the event processes such as to 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.

Figure 3: Server Explorer

Fiorano Debugger View

The Fiorano Debugger view shows the list of routes on which debugger is enabled and messages trapped within each route. This gives users the ability to take action on debug message.

Figure 4: Fiorano Debugger view

Micro Service Repository (Online Event Process Development)

In Online Event Process Development perspective, the services present in the connected enterprise server are shown in the Micro Service Repository.

The service repository can be viewed by opening the Micro Service Repository. This view which display the categorized services.

Figure 5: Micro Service Repository (Online Event Process Development perspective)

Exporting Services to Local Disk

The Services in Micro Service Repository can be exported to local disk by right-clicking the service and selecting Export to Local disk option from context menu, which opens a dialog box.

Figure 6: Export service to Local Disk

You can choose the export location by clicking the Browse button and specifying the location to be exported. By default, the selected service gets included in the export. To export Dependent services have to be selected from the tree.

Importing Services from Local disk

Components can be imported from the file system. This can be done by clicking the Import From Local Disk button.

Figure 7: Import from Local Disk

This opens a file selection dialog box with which the zip file containing services on the disk is then selected. Upon selection, the Import services dialog box appears where the services in the zip file are shown in the form of a dependency tree.

Figure 8: Import services dialog


Components that are already present are labeled in red, and those not present in the repository are labeled in black.

If the Overwrite If Exists checkbox is selected, the service in the Micro Service Repository will be over written by the one in the zip file, otherwise conflicting services are not imported from the local disk.

If the Edit <Service> (For ex: Edit chat:4.0 in figure above) checkbox is selected, after clicking Finish an information dialog appears.

Figure 9: Service Import dialog

Clicking OK opens ServiceDescriptor.xml in which the user can edit the service and save it.

Figure 10: ServiceDescriptor.xml

After closing the ServiceDescriptor.xml a dialog box appears in which the user can choose either to stop the running instances of the service or not. Clicking OK finishes the import of service from Local Disk.

Figure 11: Select an Option dialog


Adaptavist ThemeBuilder EngineAtlassian Confluence