WSO2 SOA Enablement Server for Java contains a number of useful features for persistent deployment. The first feature is that the deployment is remote. This means that there is no need for local access to the machine on which SSJ is running. The second feature is that uploading is done via SOAP. This means that all SSJ's features related to SOAP are available to deployment as well. The third feature is security. An administrator can easily forbid deployment and grant or revoke a user's rights to deploy.

Packages are created and deployed to the server using the command-line tools WSO2 SOA Enablement Server Packager, Deploy and Undeploy. These tools can also be accessed via the Administration Console GUI.

A single class or a package can be deployed. The following command line deploys the single class MyServiceImplementation, assuming the environment variables have been set and the Java class compiled:

Deploy  --target http://localhost:6060 --class MyServiceImplementation
         --uri /MyService --classpath %CLASSPATH%

Persistent deployment is described extensively in Persistent Deployment in Publishing Web services. For further information, read the Deployment Tools section of the Tools book.