The configuration file deployment.xml defines:
The file must be called deployment.xml, and must be included in the service package.
The file must be included at the top level of the service package—it cannot be in a subdirectory. There can only be one file per service package.
<Deployment xmlns="http://www.platform.com/Symphony/Deployment><install><osTypes><osType name="NTX86" startCmd="setup" timeout="600" successCodes="0,1,2"/><osType name="LINUX86" startCmd="install" timeout="100" successCodes="-1:10"/></osTypes></install><uninstall><osTypes><osType name="NTX86" startCmd="setup -u" timeout="30" successCodes=0/><osType name="LINUX86" startCmd="uninstall" timeout="34" successCodes="0"/></osTypes></uninstall><packageEnv><osTypes><osType name="all"><env name="PATH">${SOAM_DEPLOY_DIR}/bin</env><env name="env1">val1</env><env name="env2">val2</env></osType></osTypes></packageEnv><packageDependencies><package name="Common"/></packageDependencies></Deployment>
Optional. Use the install section to configure commands to run after the package is uncompressed on a compute host.
Optional. Use the uninstall section to configure commands to run if the startCmd specified in the install section fails, or before the package is removed from a compute host.