Transports Used for Access Configuration

Within a package profile, one or more transports must be defined as inbound transports used to make services publicly accessible.

Review Service Operation and Protocol Requirements for Inbound Transport Support. Based on the service operations in the service, there may be considerations for which type of inbound transport and protocol can be used to make the service publicly accessible.

Consider the following based on the type of inbound messaging transport you want to use:

Table 1. Inbound messaging transport type
Inbound messaging transport type	Considerations
JMS	If you plan to use an EAServer JMS transport as an inbound transport, it is recommended that you define queues instead of using the EAServer default queues. See the EAServer collection under Sybase WorkSpace Server Administration for more information on using EAServer Manager to add a message queue.
File	Each File Inbound transport must use a unique file directory, and two publicly accessible services in a package cannot share the same File Inbound transport. Only single thread access to a file directory is supported; a single file directory cannot be accessed by multiple services.

Within a package profile, one or more transports must be defined as inbound transports used to make services publicly accessible. These transports can be messaging transports or HTTP transports and are managed before or while defining the access configuration for a services package profile. For each package, an inventory of transports is defined and one of these transports is assigned to each public service. When the package is deployed, the package listens on the transports assigned to the public services.