Plan for Packaging

It is helpful to plan a packaging strategy before you develop a services package profile.

Consider the following:

The services to be included in the package. Multiple services can be added to the package profile, which provides you the ability to create package profiles according to your site implementation and deployment needs. However, consider the service types that your deployment server supports. Planning for Service Deployment lists the services types that can be deployed to the different runtime servers.
Endpoint configuration, which defines the endpoint binding for the service. For Sybase Services Package Profile, you can modify the endpoint binding that was used in the original service profile. You cannot change endpoint configuration for services in a EAServer Services Package Profile.
For a Sybase Services Package Profile, determine which services are to be made publicly accessible during runtime. At least one service in a package must be publicly accessible for the package to be deployable.
For each service to be published, define the following:
- The transport over which the service is publicly accessible. HTTP and messaging transports can be made available.
- The port type interface through which the service is exposed over the transport.
- The protocol type, Custom Wire, SOAP, or XML, over which the service is accessible. SOAP protocol is supported for HTTP transports.
  
  Note: All services in an EAServer Services Package Profile are publicly accessible. You do not configure the transport because the package automatically uses SOAP over HTTP.
Runtime service container configuration, including logging parameters, that may be required in your environment.