XML Schema

PTP is model-driven ; this means that its functioning and appearance are determined by a set of definitions provided via an XML file. What follows is a detailed explanation of the schema governing the resource manager XML definition. The latest version of the target configuration schema is available at the URL http://eclipse.org/ptp/schemas/v1.2/rm.xsd.

The top level of the XML configuration is the resource-manager-data type as shown in the diagram below. This type specifies all the information needed in order to submit, control, and monitor jobs on a target system.

ResourceManagerData

The resource-manager-data comprises three elements: site-data, control-data and monitor-data. In addition, a configuration name is specified using the name property. This name must be unique.

The site-data element is reserved for future use. It provides an optional place to set fixed or default remote site information. The connection strings are URIs which are specific to the PTP RemoteServices definitions. The scheme for these URIs will usually name the specific remote service (e.g, rse: or remotetools: ; local is simply file: ). The host name and port given here will appear as defaults in the resource manager selection wizard when you create a new connection.

The principal section of the schema is devoted to defining the target system control-data part. The top-level control elements include attributes, files to be staged, job script to be generated (if any), commands specific to the resource manager, and the layout of the launch configuration Resources tab.

The monitor-data section of the schema specifies the type of monitoring to be used for the target system, and any monitoring system specific information that might be necessary. If the monitor-data section is omitted, monitoring for the target system will be disabled. This is typically the case when configuring direct access to runtime systems such as MPICH2 or Open MPI.