Defining Access Configuration for a Sybase Services Package Profile

Access configuration is completed while developing a Sybase services package profile and identifies which services in a package are to be publicly accessible when the package is deployed. A publicly accessible service is a service that can be invoked by a caller outside the runtime engine. A service that has not been exposed publicly can only be invoked by other services in the same package.

The process for defining a service to be publicly accessible includes defining the following:

The transport over which the service is accessed.
The interface that is exposed over the transport.
The protocols supported when the service is accessed.

The Access Configuration page of the Sybase Services Package Profile editor is divided into these sections:

Section Name	Description
Access Configuration Settings	Specifies which services are to be made public and identifies the transport over which the service is exposed.
Exposed Interfaces	Displays all of the interfaces for the selected service and allows you to select which interfaces are to be exposed over the transport.
Protocol Settings	For each exposed interface, identifies the protocols used to expose the interface.
Transports	Displays inbound transports, HTTP or messaging, that can be used to expose services for the package. Multiple transports can be defined and are listed in this section. See Managing Transports used to Configure Service Access.

Note

The transport type and protocol combination can be restricted based on the operation types, one-way and/or request/reply, included with the service to be made public. See Service Operation and Protocol Requirements for Inbound Transport Support.

For each service in the package that is to be public, you must use the Access Configuration page to complete specific steps.

Select services for Access Configuration
Set Exposed Interfaces
Set Protocol Settings
Save the package profile.

Changes made to the access configuration on this editor page are reflected in the package profile file (<file name>.svcpkgdef) in the WorkSpace Navigator. Access configuration defined for the package profile is not reflected in the service profile.

Next: After completing access configuration, go to Configuring the Runtime Container for the Sybase Services Package Profile.