- participant
A member of a SOA network, whether service provider, service consumer, or intermediary.
- payload format
The on-the-wire structure of messages over a given transport.
In Web services, the payload format is specified using a WSDL
bindingelement.- persistent identifier (PID)
A registration property used by the OSGi Configuration Admin Service to identify a group of configuration attributes.
- physical contract
The concrete portion of a WSDL contract that defines the bindings and transport details used by the services defined by that contract. The physical contract answers questions such as:
How is message traffic formatted on the wire?
How and where does message traffic travel?
Is there more than one option for transmitting a request?
WSDL elements used in the physical contract include:
bindingelement,serviceelement,operationelement, andportelement.- point-to-point messaging
A messaging style where messages are sent between two known endpoints. This messaging style is typically implemented using queues.
- port
The physical mechanism used to access a service.
In Web services, ports are created based on the information specified in a WSDL
portelement.- processor
A Java object that performs work on a message as it passes along a route. Processors typical performs tasks like modifying the contents of a message or determining its path through a route.
- producer
An application that creates messages and posts them to a messaging destination.
- profile
A set of data that defines runtime artifacts and configuration settings for provisioning a Fabric Container.
- publish and subscribe messaging (pub/sub)
A messaging style where message producers send(publish) messages to a destination and interested consumers can register(subscribe) to receive messages from the destination. This style of messaging is implemented using topics.
 |  | |
 |
