Online Event Process Development and Offline Event Process Development perspectives are available in the eStudio application. Microservice Repository is available in both the perspectives and are explained in the below sections.
Online Event Process Development
In Online Event Process Development views, the services present in the connected enterprise server are shown in the Microservice Repository panel which displays the categorized services.
Figure 1: Microservice Repository panel
Exporting Services to Local Disk
The Services in Microservice Repository can be exported to local disk by right-clicking the service and selecting Export to Local disk option from context menu.
Figure 2: Option to export to local disk
This opens Export Service To Local Disk dialog box.
Figure 3: 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, these have to be selected from the tree as shown in the above figure.
Importing Services from Local disk
Components can be imported from the file system. This can be done by clicking the Import From Local Disk icon present in the upper-right part of the Microservice Repository panel.
Figure 4: 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 5: Import services dialog
If the Overwrite If Exists checkbox is selected, the service in the Microservice 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> (as in Edit chat:4.0 in Figure 4) checkbox is selected, after clicking Finish, an information dialog box named Service Import opens.
Figure 6: Service Import dialog
Clicking OK opens ServiceDescriptor.xml in which the user can edit the service and save it.
Figure 7: ServiceDescriptor.xml
After closing the ServiceDescriptor.xml window 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 8: Select an Option dialog
Offline Event Process Development
Fiorano eStudio has an independent Microservice Repository in Offline Event Process Development perspective, which enables services to be configured offline (without connecting to the Enterprise Server). It can be viewed by opening the Microservice Repository panel (refer Figure 1), which displays the categorized services.
Deploying Services to Server
A service can be deployed to an Enterprise server by right-clicking the component in Microservice Repository view and selecting Export Service to Server from the context menu.
Figure 9: Option to export to Server
This opens the Export Service To Server dialog box..
Figure 10: Export service to server
The dependencies are shown in a tree format. This excludes the actual Service (which gets exported by default). To export any dependencies of this Service, select the Dependency and click Finish.
If the Overwrite If Exists checkbox is selected, the services in the server will be over-written by the one in the Microservice Repository, otherwise conflicting services will not be export to the server.
Fetching Services from Server
- The services present on server can be imported into the Microservice repository by selecting the Import from Server option in the Microservice Repository panel.
Figure 11: Import from Server option
- This opens Import Service From Server dialog box.
Select the server from where services have to be imported and click the Connect button. This displays all the available services in that server.
Figure 12: Import service from server
- Select the services to be imported and click the Finish button to import the service.
Exporting/Importing Services to/from Local Disk
The components can be exported and imported from and to the file system respectively by following the same actions as performed in Online Event Process Development.