Position XML-AMQP

Running the Example in Connect

This scenario illustrates two communication paradigms. An RPC client retrieving information published by a publish/subscribe publisher. In this case an XML RPC client invokes a getPosition operation, while an AMQP service publishes position data to a position queue topic. Note, this mediator relies on the two systems being active at the same time, and makes no guarantees about the freshness of data (each get request pulls of data from the queue in FIFO fashion - hence it will not be the most recent publication).

First, start the Starlink mediator

• ActiveMQ
• java -jar InteractionEnabler.jar
• java -cp InteractionEnabler.jar Examples.Position.C2RabbitMQConnect

Next execute the XML client

• java -cp InteractionEnabler.jar;lib/xmlrpc-client-3.1.3.jar;lib/xmlrpc-common-3.1.3.jar;lib/commons-httpclient-3.0-alpha1.jar;lib/commons-codec-1.2.jar SampleApplications.Positioning.PositionClient

Finally execute the AMQP Publisher

• java -cp InteractionEnabler.jar;lib/xmlrpc-common-3.1.3.jar;lib/rabbitmq-client.jar SampleApplications.Positioning.RabbitMQPublish

Domain Specific Models

The interoperability solution is created using only domain specific models. For this implementation there are three XML files in the DSL/ApplicationAutomata/Positioning folder:

• C2Positioning.xml models the behaviour of the XML client application.
• AMQPPublisher.xml models the behaviour of the AMQP publisher application.
• C2toPositionService.xml models the interoperability merge between the two.