Service Operation and Protocol Requirements for Inbound Transport Support

As part of managing transports used for access configuration, you must consider the types of operations each service contains before exposing the service using an HTTP or messaging transport.

A service can only be exposed over a transport/protocol pair if all the operations meet the requirements for that combination. For example, a service that contains both one-way and request/reply operations can only be exposed using HTTP/SOAP. To determine what type of inbound transport is supported, review the requirements in the following table.

Table 1. Supported inbound transports
Transport type	Protocol	Supported operation type
HTTP	SOAP	One-way operations; request/reply operations
Message (e-mail, JMS, file)	XML, CWF (depending on the interface)	One-way operations

Additionally, the following requirements must be met:

A message definition for a custom wire format is only supported over a messaging transport for services with one-way operations each containing a single parameter that references a Message Designer-generated schema.
SOAP is supported if all of the operation parameters reference a namespaced schema.

Send your feedback on this help topic to Sybase Technical Publications: pubs@sybase.com

Your comments will be sent to the technical publications staff at Sybase, Inc. For product-related issues or technical support, contact Sybase Technical Support at 1-800-8SYBASE.