Create the packages for each target server using the custom configuration specified when creating the deployment profile and deploy the package to the corresponding target servers.
After you develop a Sybase services package profile or an EAServer services package profile, use the service package profile to deploy the physical package.
You can deploy a package immediately after using the wizard if all required service definitions included in this initial package are complete. In this case, the package is generated using defaults and you do not use the editor to further develop the package profile. The generated package profile uses the following defaults:
Public access using the SOAP protocol over an HTTP transport for all services explicitly added to the package. Dependent services are automatically included but are not publicly accessible.
All service interfaces and operations defined as visible for the included public services are exposed.
Logging level set as critical.
The custom configuration that you specified on the Configuration page of the editor is used to deploy the package.
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.