Deploy a service package
To use a new application, you must deploy the service binary to your cluster. Using the soamdeploy add command to update an existing package will not terminate the current running workload. You can also deploy the service package to a non-leaf consumer, so that all applications registered to child leaf consumers are able to share the same service package.
Deploy a service package with your own deployment tool
You do not want to use the deployment tool distributed with Symphony to deploy your service packages. You have your own tool but want it to work with Symphony. You do not need to create a service package to use your own deployment tool.
Deploy a service package without a deployment tool
You do not need to use the deployment tool distributed with Symphony to deploy your service packages. You want to skip the deployment step altogether, and still be able to tell Symphony where the service binaries are located on each machine.You may need to do this because you image your compute hosts with the service binaries already on the machines, or service binaries are in a shared location, so deployment is not necessary.
Automatically run a command when deploying a service package
Suppose your service uses a third-party tool and it needs to be installed on the compute host, or you want to run a script to perform some actions for proper functioning of the service program. You can configure this in a package-specific deployment.xml configuration file.