This component is aimed at demonstrating the working of the Component Control Protocol. This sample shows how to handle the events sent from the peer server and how to send service status to the peer server.
By default, there is no business logic or send logic implemented in the component's code. So it doesn't send out any message to the output port.
For additional information on CCP refer to the Component Control Protocol (CCP) section in the Enterprise Edition Online Documentation.
Changes required to support CCP are as below.
1. The following classes are added to support CCP.
|com.fiorano.edbc.ccpcomponent.ccp.jms.CCPEventHandler||listens to the events generated by peer server and handles those events.|
|com.fiorano.edbc.ccpcomponent.ccp.jms.CCPEventGenerator||sends the events from component as JMS messages to the peer server.|
|com.fiorano.edbc.ccpcomponent.ccp.jms.CCPEventManager||Manages the life cycle of CCPEventHandler and CCPEventGenerator.|
|com.fiorano.edbc.ccpcomponent.ServiceState||Holds the state of the service at a particular instant.|
|com.fiorano.edbc.ccpcomponent.ccp.ServiceStateListener||Monitors the service state and notifies a change in the service sate.|
2. The following changes are made to the generated JMSSample component.
Add and implement the method