...
- Drag one Feeder and one Display component from Micro Service Palette under Util category.
- Connect the components in the following manner:
- Feeder component output port to SocketClient input port.
- SocketClient output port to Display component input port.
Figure 9: Adding Display components to SocketRW_Client_Eg event process
Understanding the Data Flow
Data flows in the following order:
...
- Click Check Resource and Connectivity
icon (or press ALT+SHIFT+C) to check resource and connectivity.
- Click Run Event Process
icon (ALT+SHIFT+R) to run the event process. DisplayMessage and DisplayStatus windows get open.
- Switch to SocketRW_Client_Eg Event Process Orchestrator and follow steps 1 and 2 above. Feeder1 and Display1 components get open.
- In the Client Feeder1 window, replace 'Input Text' with 'TestMessage' and click Send.
Figure 11: Sending message from Feeder
- DisplayMessage window displays the message from the client that is received by serverthe server.
Figure 12: Displaying Message received from client
- DisplayStatus shows the confirmation message 'Message Sent Successfully' when as the server writes the message back to the client.
Figure 13: Status message indicating that message is written back to client
- Display1 receives the message that is sent back from Serverthe server.
Figure 14: Message sent back by Server, received by the client
Anchor | ||||
---|---|---|---|---|
|
- Download SocketRW_Server_Eg and SocketRW_Client_Eg event processes and Import the Event Processes to the Event Process Repository in the Server Explorer in eStudio to understand the configuration used in this example and to execute the working sample.
- Please note that the options used in this example are minimum, which helps you to get an overview of the application. To explore the other options present in the SocketAdapter, Feeder and Display, refer sections: SocketAdapter, Feeder and Display respectively.
Overview
Content Tools
ThemeBuilder