Package

During the packaging phase, you develop a package profile and create the package. The package profile is used to create the physical package that is deployed in a runtime environment.

There are two types of package profiles:

A Sybase Services Package Profile allows deployment of services to the Service Container or EAServer with the Common Service Bus add-on runtime server.
An EAServer Services Package Profile allows deployment of Java services to the EAServer 5.x or EAServer 6.x Web Services Toolkit runtime server.

Some service types can be deployed only to the Service Container runtime server. Planning for Service Deployment lists the services types that can be deployed to the different runtime servers.

A services package profile allows you to define the services to be included in the package and the configuration for endpoint and runtime specifications.

You can also configure access specifications for Sybase Services Package Profiles. The package profile is a reference to the included services but does not actually include the services.

Plan for Packaging
It is helpful to plan a packaging strategy before you develop a services package profile.
Developing a Sybase Services Package Profile
The Sybase services package profile is used to create the physical services package.
Developing an EAServer Services Package Profile
Develop an EAServer Services Package Profile that can be used to create a physical EAServer 5.x or EAServer 6.x services package.
Creating a Services Package
After you develop a services package profile, you can use the services package profile to create the physical package, which can also be called the artifact, or you can develop a deployment profile and use the deployment profile to create the physical 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.