Use the Deploy Service to deploy packages to WSO2 SOA Enablement Server. To learn about Deployment and Undeployment of Web services, please see Publishing Web services.
The Deploy Service SOAP endpoint is accessible at http://localhost:6060/admin/deployservice (assuming that the WSO2 SOA Enablement Server is running on localhost and default ports). Note that if the WSO2 SOA Enablement Server is running in secure mode, then this service is protected both by authentication and authorization.
The DeployService is included in the Core-Services component (please see Core-Services in the Components chapter).
For complete information about the Deploy Service, including a list of methods, please check either the Deploy Service Javadoc, org.systinet.wasp.admin.DeployService or its WSDL.
When the server starts, it scans the application directory to get information about all installed packages. If an error occurs with an installed package, for instance, because it cannot be registered or loaded, its package.xml file and wasp.xml are renamed to package.ignore and wasp.ignore before booting can continue.
When there are some packages dependent on the ignored package, they will be recursively set to ignored.
When the server starts, it logs information about all ignored packages.
The simplest way to destroy these packages is to stop the server, delete the relevant directories and try to deploy repaired packages once more. In case of some dependents you have to do it for all of them.
If an error occurs when using Deploy Service, an org.systinet.wasp.admin.PackageException is thrown.
For further details on the Deploy Service methods please check either its Javadoc or its WSDL.