MyLEAD Relay Agent

As part of the LEAD project, our infrastructure is currently being integrated with the LEAD portal. This agent represents the first of several steps to achieve this integration. Its position in our messaging system can be seen in the message bus diagram.

Purpose

To store workflow and file metadata associated with brokered submissions using the MyLEAD Metadata Catalog.
To translate our LocalEvents into WS-Events and place them on the Message Bus used in connection with the LEAD portal.

Design

The structure of the relay agent is straight-forward. The main component listens for events on our event bus, and delegates the event to the appropriate event handler. Each handler has a reference to the notifier factory and/or workspace manager, depending on the type of event. Appropriate actions are taken on the notifier or the MyLEAD agent, as indicated in the following table:

Event	Status	LEAD Component	Action
Debug		`edu.indiana.extreme.lead.workflow_tracking.Notifier`	`debug()`
Error		`edu.indiana.extreme.lead.workflow_tracking.Notifier`	`exception()`
Status	WORKFLOW SUBMITTED	`edu.indiana.extreme.lead.workflow_tracking.Notifier`	`workflowInvoked()`
Status	WORKFLOW CANCELLED	`edu.indiana.extreme.lead.workflow_tracking.Notifier`	`workflowTerminated()`
Status	WORKFLOW FAILED	`edu.indiana.extreme.lead.workflow_tracking.Notifier`	`workflowTerminated()`
Status	WORKFLOW DONE	`edu.indiana.extreme.lead.workflow_tracking.Notifier`	`workflowTerminated()`
Status	NODE PENDING	`edu.indiana.extreme.lead.workflow_tracking.Notifier`	`invokingService()`
Status	NODE SUBMITTED	`edu.indiana.extreme.lead.workflow_tracking.Notifier`	`serviceInvoked`
Status	NODE ATTEMPTED	`edu.indiana.extreme.lead.workflow_tracking.Notifier`	`invokingServiceFailed`
Status	NODE QUEUED	`edu.indiana.extreme.lead.workflow_tracking.Notifier`	`jobStatus()`
Status	NODE ACTIVE	`edu.indiana.extreme.lead.workflow_tracking.Notifier`	`jobStatus()`
Status	NODE CANCELLED	`edu.indiana.extreme.lead.workflow_tracking.Notifier`	`sendingResult()`; `serviceTerminated()`
Status	NODE FAILED	`edu.indiana.extreme.lead.workflow_tracking.Notifier`	`sendingResult()`; `serviceTerminated()`
Status	NODE DONE	`edu.indiana.extreme.lead.workflow_tracking.Notifier`	`sendingResult()`; `serviceTerminated()`

The relay agent is booted with a properties file indicating the appropriate endpoints for WS Event notifications and the MyLEAD Agent service:

#NCSA event bus
eventListener.tag.1=loggingListener
eventSender.0=tcp://tb1.ncsa.uiuc.edu:61616,ncsa.tools.jms.localevent.JMSLocalEventSender
eventReceiver.0=tcp://tb1.ncsa.uiuc.edu:61616,ncsa.tools.jms.localevent.JMSLocalEventReceiver
receiveTopic.0=TROLL

#IU Message Broker
wsmg.broker.url=http://tyr11.cs.indiana.edu:12346/
#loopback=false

#MyLEAD agent
mylead.agent.url=https://tyr03.cs.indiana.edu:20243/myleadagent?wsdl
credential.file=hostcertkey-tb1.ncsa.uiuc.edu.pem
trusted.certs.file=trusted_cas.pem
fixed.properties.file=fixed.properties
dn.properties.file=dn.properties

#JDBC gridmap db
gridmap.connection.url=jdbc:mysql://localhost/brokerstore
gridmap.connection.username=mysql
gridmap.connection.password=mysql

Child pages

MyLEAD Relay Agent

As part of the LEAD project, our infrastructure is currently being integrated with the LEAD portal. This agent represents the first of several steps to achieve this integration. Its position in our messaging system can be seen in the message bus diagram.

Purpose

Design