{center}
{flash:file=Architecture^soceda_architecture.swf|width=581px|height=486px}
{center}
h2. Functionality
The Proxy Event Manager is able to maintain the list of Event Producers for a given topics. It can
be considered as a broker for Event Producer.
h2. Technical requirements
The Proxy Event Manager is a native service directly integrated in [PEtALS DSB|soceda:DSB].
The Source Code is available at: [https://svn.petalslink.org/svnroot/trunk/research/dev/experimental/easyevent/proxy-event-manager]
h2. Components architecture
!EventProxyManager.png|align=center!
The behaviour of proxy event manager (PEM) is explained in animations below:
{table-plus}
|| Animation || Description ||
| {center}{flash:file=^PEM_Initialization.swf|width=600px|height=560px}{center} | {section}*_initializations_*: Once ESB and EasierGOV are conntected (see [easiestdemo:How-to connect EasierGOV to EasyESB]) and Web Services of providers binded to the infrastructure of services, EasierGov is able to detect the Event Producers among the Web Services. {section}|
| {center}{flash:file=^PEM_Subscriber.swf|width=600px|height=560px}{center} | {section}*_subscriber mode_*: When a Event consumer want to subscribe on a specific topic, it send its subscription to PEM. The PEM invokes EasierGOV to known all Event producer able to provide the required topic and send subscriptions to all providers found.{section} |
| {center}{flash:file=^PEM_Dynamicity.swf|width=600px|height=560px}{center} | |
{table-plus}
{flash:file=Architecture^soceda_architecture.swf|width=581px|height=486px}
{center}
h2. Functionality
The Proxy Event Manager is able to maintain the list of Event Producers for a given topics. It can
be considered as a broker for Event Producer.
h2. Technical requirements
The Proxy Event Manager is a native service directly integrated in [PEtALS DSB|soceda:DSB].
The Source Code is available at: [https://svn.petalslink.org/svnroot/trunk/research/dev/experimental/easyevent/proxy-event-manager]
h2. Components architecture
!EventProxyManager.png|align=center!
The behaviour of proxy event manager (PEM) is explained in animations below:
{table-plus}
|| Animation || Description ||
| {center}{flash:file=^PEM_Initialization.swf|width=600px|height=560px}{center} | {section}*_initializations_*: Once ESB and EasierGOV are conntected (see [easiestdemo:How-to connect EasierGOV to EasyESB]) and Web Services of providers binded to the infrastructure of services, EasierGov is able to detect the Event Producers among the Web Services. {section}|
| {center}{flash:file=^PEM_Subscriber.swf|width=600px|height=560px}{center} | {section}*_subscriber mode_*: When a Event consumer want to subscribe on a specific topic, it send its subscription to PEM. The PEM invokes EasierGOV to known all Event producer able to provide the required topic and send subscriptions to all providers found.{section} |
| {center}{flash:file=^PEM_Dynamicity.swf|width=600px|height=560px}{center} | |
{table-plus}