Configure the Symphony—MoSes application

To distribute MoSes work units to the grid, you need to deploy the Symphony—MoSes service. To use it, you need to have an application associated with your service.

The installation package contains an application profile to register in your cluster.

Modify the MoSes application profile Moses6App.xml located in <SYM_MOSES_HOME>\service.
  1. In the Consumer section, if you have created a different consumer and/or resource group for the Symphony—MoSes application, change the consumerId and/or resourceGroupName, respectively.
    <Consumer applicationName="MosesApp"
     consumerId="/SampleApplications/SOASamples"              resReq="" policy="R_Proportion" resourceGroupName="ComputeHosts"..."/>
  2. In the SSM and SIM sections:
    1. Add SOAM_HOME to indicate the soam subdirectory under the directory in which Symphony is installed. For example, if Symphony 5.1 is installed in c:\Symphony, specify c:\Symphony\soam as your SOAM_HOME.
      ... 
          <SOAM>
            <SSM resReq="NTX86" resourceGroupName="ManagementHosts">
                  <osTypes>
                      <osType name="NTX86" 
                         ...
                        <env name="SOAM_HOME">C:\symphony\soam</env>                                  ...                </osType>            </osTypes>            ...      </SSM>      <SIM>            <osTypes>                <osType name="NTX86"                   ...               <env name="SOAM_HOME">C:\symphony\soam</env>                   ...                </osType>            </osTypes>       ...
    2. Delete the following line:

      <env name="VERSION_NUM">3.1</env>

  3. In the Service section, change the fileNamePattern for the service log:
    <osTypes>
     <osType name="all" startCmd="${SOAM_DEPLOY_DIR}
    \MoSesService.exe" fileNamePattern="mosesint.service"
     logDirectory="${SOAM_HOME}/logs"
     workDir="${SOAM_HOME}/work">
      <env name="MOSES_INT_LOGLEVEL">INFO</env>
     </osType>
    </osTypes>
  4. In the Service section, add the Control section:
    ... 
    </osTypes>
     <Control>
       <Method name="Invoke" >
         <Timeout duration="0" actionOnSI="restartService" actionOnWorkload="retry" />
         <Exit actionOnSI="restartService" actionOnWorkload="retry" />
         <Return controlCode="0" actionOnSI="keepAlive" actionOnWorkload="succeed"/>
         <Exception type="failure" controlCode="0" actionOnSI="keepAlive"
         actionOnWorkload="retry"/>
         <Exception type="fatal" controlCode="0" actionOnSI="keepAlive"
         actionOnWorkload="fail"/>
       </Method>
    </Control>
    </Service>
    ...