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.

To use the service package profile to create the physical package:

In the WorkSpace Navigator, select the services package profile you want to use to create the package.
Right-click the services package profile and select Build Package.
The Package Constructors Selection dialog appears.
Select the type of container to be used to create the services package and click OK. Your selection is based on the server type to which the package is to be deployed.

After the Services Package file is created, the artifact is displayed in the WorkSpace Navigator. Sybase Services Package files have a .svcpkg extension; EAServer 5.x Services Package files have a .jar extension.

Note

The property that defines the number of threads used for an inbound JMS transport is defined manually after the services package is created. See Configuring Threading for a JMS Inbound Transport.

Select a method for creating a services package based on the intended deployment method:

If you are going to deploy the package using the Sybase WorkSpace framework, create the package using the package profile and the deployment profile.
If you are going to deploy the package outside the Sybase WorkSpace framework, create the package without a deployment profile.
The create package without a deployment profile process creates an artifact that is deployed manually to a server.