Chapter 4: ServiceMap Document: Advanced Features

The services created by the toolkit offer some advanced features that you can enable from the ServiceMap document.

<method userDefined="false">
    <methodName>Ping</methodName>
    <methodDescription>Just ping the service</methodDescription>
</method>

<method userDefined="false">
    <methodName>Shutdown</methodName>
    <methodDescription>Shutdown the service</methodDescription>
</method>

<method userDefined="false">
    <methodName>Kill</methodName>
    <ethodDescription>Kill the service</methodDescription>
</method>

Note: The 'Shutdown' and Kill methods can be invoked directly or indirectly by sending either a SIG_TERM (TERM signal), SIG_HUP (caused by a log out) or by a SIG_INT (cause by control-c) to the service.

<application>
    <applicationName targetNamespace="http://www.extreme.indiana.edu/lead">TestApp</applicationName>
    <project>
        <projectName>TG-ASC060000N</projectName>
        <projectDescription>LEAD Account on TeraGrid</projectDescription>
    </project>
    <queue>
        <queueName>test_queue</queueName>
        <queueDescription>Test queue</queueDescription>
    </queue>
    <count>
        <value>10</value>
        <decription>Run 10 counts of the application<description>
    </count>
    <!-- The application is an MPI applications -->
    <jobType>mpi</jobType>

</application>

The "projectName" is the account string used to execute the application. The "queueName" is the queue to submit the job if there is a batch scheduler on the cluster. The "count" is the number counts of the application to run. If the application is an MPI (Message Passing Interface) application, the "jobType" must be specified as "mpi".

<ServiceMap>

    <lifeTime>
        <notAfterInactiveMinutes>60</notAfterInactiveMinutes>
    </lifeTime>

</ServiceMap>

[ << ] [ < ] [ Home ] [ > ] [ >> ]