After developing a Java service, you move to the Package phase. Develop an EAServer 5.x Services Package Profile that can be used to create a physical EAServer 5.x services package.
The following workflow guides you through the development process. For assistance in performing these tasks, open the Developing an EAServer 5.x Services Package Profile cheat sheet.
Complete prerequisites.
Have EAServer 5.x running.
Develop services, keeping in mind the service types supported for EAServer WST deployment as described in Planning for Service Deployment.
Create an EAServer 5.x Services Package Profile using the Services Package Profile wizard.
When finished with the wizard, the Package Profile editor opens.
If all service profiles included in the package are complete, the generated package is ready to deploy. Deploying a Services Package contains the defaults that are used when deploying at this stage.
Complete the package profile. You can define the following package profile details, although the package can be deployed using the defaults.
On the Introduction page, learn more about using the package profile editor.
On the Contents page, update the contents of the services package profile.
On the Endpoint Configuration page, configure endpoints for the package profile.
On the Services page, edit the package by adding or removing a service to or from your package profile.
On the Handlers page, add, edit, or remove special global handlers to or from your package profile.
On the Handler Chains page, add, edit, or remove groups of handlers to or from your package profile.
On the Global Configuration page, set configuration to be used by everything in the package.
On the Transports page, specify handlers and parameters for the transports.
On the Type Mappings page, map between a Java class and SOAP data.
On the Runtime Container Configuration page, configure the runtime container and logging.
At this stage, you can do one of the following:
Continue with the process by adding the defined service package to a Deployment Profile.
Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com