 <tasks-configuration xmlns:svns="http://org.wso2.securevault/configuration">

    <!-- 
      The currently running server mode; possible values are:-
      STANDALONE, CLUSTERED, REMOTE, AUTO.
      In AUTO mode, the server startup checks whether clustering is enabled in the system, 
      if so, CLUSTERED mode will be used, or else, the the server mode will be STANDALONE.
    -->
    <taskServerMode>AUTO</taskServerMode>
    
    <!-- 
      To be used in CLUSTERED mode to notify how many servers are there in 
      the task server cluster, the servers wait till this amount of servers
      are activated before the tasks are scheduled -->
    <taskServerCount>2</taskServerCount>

     <!--
      You can explicitly configure task repository class
      FileBasedTaskRepository is supported in only micro ei profile where multitenancy and clustering is disabled-->
     <!--<taskRepositoryClass>org.wso2.carbon.ntask.core.impl.FileBasedTaskRepository</taskRepositoryClass>-->


     <!-- The default location resolver configuration -->
    <defaultLocationResolver>
        <locationResolverClass>org.wso2.carbon.ntask.core.impl.RoundRobinTaskLocationResolver</locationResolverClass>
    </defaultLocationResolver>

    <!-- 
      if task-type-pattern matches and task-name-pattern matches, check existing addresses of address-pattern,
      and if addresses exist, select address in round-robin fashion, if not move onto next rule in sequence.
      <property name="rule-[order]">[task-type-pattern],[task-name-pattern],[address-pattern]</property>
    -->
    <!--defaultLocationResolver>
        <locationResolverClass>org.wso2.carbon.ntask.core.impl.RuleBasedLocationResolver</locationResolverClass>
        <properties>
            <property name="rule-1">HIVE_TASK,.*,192.168.2.*</property>
            <property name="rule-5">.*,.*,.*</property>
        </properties>
    </defaultLocationResolver-->

    <!-- The address to which the remote task server should dispatch the trigger messages to, 
      usually this would be an endpoint to a load balancer -->
    <taskClientDispatchAddress>https://localhost:9448</taskClientDispatchAddress>
    
    <!-- The address of the remote task server -->
    <remoteServerAddress>https://localhost:9443</remoteServerAddress>
    
    <!-- The username to authenticate to the remote task server -->
    <remoteServerUsername>admin</remoteServerUsername>
    
    <!-- The password to authenticate to the remote task server -->
    <remoteServerPassword>admin</remoteServerPassword>

    <!-- Below contain a sample to be used when using with secure vault -->
    <!--remoteServerPassword svns:secretAlias="remote.task.server.password"></remoteServerPassword-->

     <!-- The task service availability of remote task server-->
     <taskServerAvailabilityCheck>
         <retryCount>10</retryCount>
         <!--time interval(milliseconds) between availability check -->
         <retryInterval>1000</retryInterval>
     </taskServerAvailabilityCheck>

</tasks-configuration>
