Writing a Simple ApplicationDescription Document

We mentioned in Chapter 1 that an application is uniquely identified by a fully qualified name (QName). An ApplicationDescription document identifies a particular deployment of an application. A sample is given below. For more details, refer its schema. This document is usually written by the application provider and must be registered with a well known Registry service.

<ApplicationDescription xmlns="http://www.extreme.indiana.edu/namespaces/2004/01/gFac"
    xmlns:lead="http://www.extreme.indiana.edu/lead">

    <applicationName targetNamespace="http://www.extreme.indiana.edu/lead">TestApp</applicationName>

    <deploymentDescription>
        <hostName>rainier.extreme.indiana.edu</hostName>
        <executable>/tmp/testApp</executable>
        <workDir>/tmp</workDir>
        <tmpDir>/tmp</tmpDir>
        <applicationEnv>
            <name>envName1</name>
            <value>envValue1</value>
            <name>envName2</name>
            <value>envValue2</value>
        </applicationEnv>
        <jobType>mpi<jobType>
    </deploymentDescription>
</ApplicationDescription>
 

The "hostName" specifies the name of the host on which the application has been deployed. The "executable" is the path to the actual application on that host. The "workDir" is optional and specifies the working directory for that application. The "tmpDir" is also optional and specifies the temporary directory for running the application. The temporary directory is usually used by the service to store the standard out, standard error and temporary files of the application. The environment variables to be passed to the application can be specified using the "applicationEnv". If the application is an MPI application then you need to specify it using the "jobType". This will tell the application service can run the application as an MPI application.

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