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.

  • If the service binaries are in a shared location, service binaries and any other additional files required by the service must be accessible to all compute hosts

  • If service executables are locally installed on compute hosts, the service executables must be in the same location on all compute hosts

  • Symphony grid only. The OS user account assigned to the consumer for the application must have permissions to execute the service binaries on compute hosts

  1. In the Platform Management Console, create an application with the Add/Remove Application wizard.
  2. Click Configure Applications and select the application to modify.

    The Application Profile window displays.

  3. Click Export and save it to a file.
  4. In an XML editor, open the application profile and edit the Service section:
    1. For PreExecCmd , specify the command to run for your deployment tool to deploy your service on to the compute hosts.
    2. For StartCmd , specify the location of the service binary on the compute host after the deployment command has run. This location must be the same on all compute hosts.
    3. In workDir, specify the working directory for your service.

      On Windows:

      For example, if your deployment command is called deploy:

      <Service name="myservice" description="My Sample Service">        
      ...
      <osType name="all" preExecCmd="C:\mydeploytool\bin\deploy.exe download -a myservice" startCmd="C:\myservices\myservice\myservice.exe"                     
      workDir="C:\myservices\myservice\work">
      </osType> 
      ...
      </Service>

      If working directory is not specified, by default, %SOAM_HOME%\work is used for service instances.

      On Linux/UNIX:

      <Service name="myservice" description="My Sample Service">        
      ...
      <osType name="all" preExecCmd="/mydeploytool/bin/deploy download -a myService" startCmd="/myservices/myservice/myservice" workDir="/myservices/myservice/work">
      </osType>
      ...
      </Service>
  5. Click Configure Applications and select the application to modify.

    The Application Profile window displays.

  6. Click Import and browse to select the changed application profile, then click Import.
    Note:

    You can also use the soamreg command to register your new application profile.

  7. Click Save to save your changes.