Service Interface

The Service Interface section describes the means by which the underlying capabilities of a service are accessed. It tells a service requester how to construct an invocation message and interpret a response message.

The Service Interface page contains the following information:

• Name (required): The name used to identify the interface.
• Description:A short passage that describes the interface. NOTE: For JMS-based services, this description should also include the version of the JMS API specification used by the service.
• Interface Type (read-only):A value indicating the kind of technological solution deployed by the service. NOTE: This value is assigned in the Service Profile section. Values are:

Method-oriented	An interface that exposes service capabilities through a set of operations. Technologies that support this interface type are Web Service framework (WS*) and OGC Web Common Services.
Message-oriented	An interface that exposes service capabilities through creating, sending, receiving, and reading messages exchanged by distributed systems. The middleware technologies that support this interface type include Java Message Service (JMS) and .NET WCF.
Resource-oriented	An interface that supports the REST architectural style of interactions, that is, manipulation of XML representations of Web resources using a uniform set of stateless operations, usually a set of HTTP methods.

• Messaging Model (read-only): A value indicating the type of model implemented by a message-oriented interface. NOTE: This value is assigned in the Service Profile section. Values are:

Publish/Subscribe	A messaging model that supports publishing messages to a particular message topic. Subscribers may register interest in receiving messages on a particular message topic.
Point-to-Point	A messaging model in which messages are routed to an individual consumer that maintains a queue of incoming messages. Each message is addressed to a specific queue, and the receiving clients extract messages from the queues established to hold their messages. While any number of producers can send messages to the queue, each message is guaranteed to be delivered to and consumed by one consumer.