Page History

...

Event Processes are composite applications created as event-driven assemblies of service microservice components. They represent the orchestration of data flow across customized Service Components microservice components distributed across the ESB network. 

Event Processes in Fiorano are designed to connect disparate applications in a heterogeneously distributed environment. Event Processes allow the logical process design to be mapped directly to physical service microservice components distributed across the ESB network.

...

A Chat component initiates a chat session on two or more nodes of a Fiorano Network. This event process also demonstrates how messages flow from one service microservice to the other in a Fiorano Network. 

...

1. Create an new Event Process with a unique name (saved as 'Chatting_Test' in this example) that represents the process.
2. In the Server Explorer, under the category where the new Event Process is added (for example, Event Process7), do any one of the two actions below:
   • Double-click the Event Process.
   • Right-click the Event Process and click Open.

   Info
   Fiorano Orchestrator turns to a white screen, bearing the Event Process name on the title. The format of this name is: <EP Name>:<Version number> [Environment]Environment can be changed in Properties section.

3. Bring the component to the Fiorano Orchestrator following any one of the below 2 options:
   • Right click on the Fiorano Orchestrator, go to Insert and click Service Instance
     
     
     
     

   • Click the respective service microservice on the Micro Service Palette to display the components under the particular service microservice and drag the component to the Fiorano Orchestrator.
     
     

     Note
     In case the Micro Service Palette is not visible, open it from Show View in Window menu.

4. Repeat the above action to bring another chat component.

   Info
   You can see that these components carry default names: chat1 and chat2.

...

After adding the components, they need to be linked by an Event Route so that  data flows between the two service microservice instances. 

To create a route between the two components, perform the following actions:

...

Sample Event Processes are predefined examples that come with the eStudio where components will be configured and connected making it ready to work/execute. A new Event Process can be created or build-upon these predefined ones by saving it into a different category and customizing it as required.
To create an Event Process from a Sample Event Process:

1. In the Server Explorer palette of eStudio, double-click (or right-click and select Login) EnterpriseServer to login to Enterprise Server.

   Note: Service Explorer palette

   Note
   Server Explorer palette generally appears by default on opening the application, but in case it does not appear, open it

   from

   from Window

   →

   > Show View).

   
   Image Modified
   
   

2. Double-click (or click on the Expand button) EnterpriseServer, right-click Event Process Repository, and then click Add Sample Event Process.
   
   
3. In the Add Sample Event Process dialog box, choose the required examples by selecting the check boxes adjacent to the Event Process names or choose all of them by clicking Select All button and then click Finish. The Samples are available under Event Process Repository.
   
   
4. In the Event Process Already Exists pop-up, click the below buttons as required:
   
   
   
   
   • Rename: An Event Process Customization page dialog box appears where either of the below can be done:
     
     
     • Change the name and click Finish to save the Sample Event Process with a new name in the Sample Event Process list.
     • Change the Category by choosing from the Category drop-down or typing a new name which creates a new Category.
   • Overwrite: Overwrites the Event Process to the predefined ones that come along with the system. This is used when any changes are made to the predefined sample, which needs to be reverted to the original one.
   • Ignore: Closes the dialog boxes without any changes made.
   • Ignore All: Does the same as Ignore, but used for more than one item selected (where all of them need to be ignored and dialog boxes closed)

Using a Remote

...

Microservice Instance in an Event Process

To add a component from an existing Event Process, right-click the Orchestrator, go to Insert and click Remote Service Instance. Then select the required component and click OK.

...

...