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.
Before assigning inbound transports for access configuration:
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:
| Inbound Messaging Transport Type | Considerations |
|---|---|
JMS | If you are planning 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. |
Use the Transports section of the Access Configuration page of the Services Package Profile editor to manage this inventory of transports.
To add a transport:
Click Add... The New Transport wizard opens.
Select the transport type and click Next. The options are Messaging Transport and HTTP transport.
Choose one of the following:
If the transport is an HTTP transport, enter a name and description for the transport and click Finish. The name of the transport must exist on the server and the name must match the name referenced by that transport.
If the transport is a messaging transport:
Type a name and description for the transport, then click Next. The name provides an internal reference to the transport.
Select the type of messaging transport that is to be used and click Next.
Specify the connection properties for the messaging transport. Choose one of the following and click Next:
Reference the connection properties using an endpoint defined by a connection profile in the Enterprise Explorer. Click Browse and locate the endpoint reference.
After the connection profile is selected, the table displays the profile's connection properties so that you can verify they are correct.
If you are using a JMS connection profile, verify that the Initial Context Factory and Queue Connection Factory properties are correct for your JMS provider type and site implementation. Some JMS providers allow multiple names for these properties.
Provide user-specified connection properties.
Set runtime properties for the inbound transport and click Next.
The property that defines the number of threads used for an inbound JMS transport is defined manually after the services package is created. See Configuring Threading for a JMS Inbound Transport.
Review the Summary page and click Finish. To make changes, click Back until the appropriate page displays, make the change, and complete the wizard.
To delete a transport:
Select a transport in the Transports section.
Click Delete.
Click OK to confirm that you want to delete the transport and its associated access configuration settings.
Next: When the inventory of transports is complete, you are ready for Defining Access Configuration for a Services Package Profile.
Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com