Service package deployment

Learn about service package deployment.

Service package deployment and removal process
The package deployment process has two phases: First, service packages are copied to the central repository on the repository server, the host on which the rs service is running. Then, when workload comes in, the service package is copied to compute hosts and uncompressed.
Deploying a new application
You developed a new service, compiled it, and are now ready to use it in your cluster. To use the new service, you must deploy it to compute hosts and associate it with an application.
Deploying a MapReduce application
You have compiled your MapReduce application and are ready to run and test the application within your IBM® Spectrum Symphony DE cluster.
Deploying a MapReduce application to the production grid
Deploying 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.
Registering a new application
Removing an application
You can remove application binaries from the system.
Deploying a service package with your own deployment tool
You do not want to use the deployment tool distributed with IBM Spectrum Symphony to deploy your service packages. You have your own tool but want it to work with IBM Spectrum Symphony. You do not need to create a service package to use your own deployment tool.
Deploying a service package without a deployment tool
You do not need to use the deployment tool distributed with IBM Spectrum Symphony to deploy your service packages. You want to skip the deployment step altogether, and still be able to tell IBM Spectrum 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.
Multiple services in an application

Parent topic: Application deployment and management