Amsterdam Server 3.0-RC1 API

Amsterdam Server API and implementation.

See:
Description

Packages

org.backsource.amsterdam
org.backsource.amsterdam.cron
org.backsource.amsterdam.cron.qcron
org.backsource.amsterdam.deployment
org.backsource.amsterdam.deployment.jboss
org.backsource.amsterdam.metadata
org.backsource.amsterdam.service
org.backsource.amsterdam.service.filter
org.backsource.amsterdam.service.jboss
org.backsource.amsterdam.service.protocol
org.backsource.amsterdam.service.protocol.feature
org.backsource.amsterdam.service.publisher
org.backsource.amsterdam.service.strategy
org.backsource.amsterdam.service.workerqueue

Amsterdam Server API and implementation.

What is the Amsterdam Server Service

The Amsterdam Server Service is a container specialized in setting up a so called channels. A channel is a configurable chain of handlers that helps in getting/receiving data, handling data and publishing data. To learn more about Amsterdam one should read the Amsterdam Server Manual.

Develop Amsterdam Components

To develop new Amsterdam components that works in a channel, one have to implement and use several of the API:s and implementations contained in these packages.

An amsterdam channel consists primarily of the layers:

1. The invocation layer. This layer is responsible for getting messages into the system. This may be either a pulling fetcher, called a GETServiceInvoker or a passively receiving sink called a RECServiceInvoker. The invocation layer uses a ProtocolFactory for the messages to be fetched or received. This layer created a ServiceMessage that travels through the invocation chain.
2. The filter layer. The ServiceMessage is run through a chain of filters ServiceFilter, which may act on the message, such as transforming it, backing it up to storage or stop further invocation.
3. The publishing layer. Last in the chain is the publisher Publisher, which logically has the responsibility to transport the message somewhere out of the system, such as publishing to a JMS destination.

Other API:s of importance is the Servable interface which defines the lifestyle methods of Amsterdam components, XmlConfigurable which marks a component as taking an XML configuration part to set itself up.