configfile — Declare a file that must be configured by the user.


A package may contain configuration files for the packaged software. These files will be configured from the GUI by the user. The configfile will contain several sub tags, which define tokens that will be replaced in the file.


  • packagefile (required) - The name of the file as it is contained in the package.

  • remotefile (required) - The name of the file as it should be on the remote system. This can be a relative pathname (ex. src/file.conf).

  • description (optional) - A description of the file's purpose or conventions.

  • forceConfigure (optional) - If forceConfigure="true" the user will be required to edit the file, even if they are not in Advanced Mode in the ReST application. If forceCongfigure is not declated or forceConfigure="false" the defaults will be used for all substitutions.


The following elements are valid parents of configfile: header.


The following elements are children of configfile: sub.


Example 12. Configfile XML Example

<configfile packagefile="server_config" 
                description="NetSolve Server Configuration File">
  <sub name="nproc" description="Number of processors"
       default="2" type="string"/>
  <sub name="agent" description="The NetSolve Agent hostname"
       default="" type="string"/>
  <sub name="scratch" description="Scratch Directory"
       default="/tmp/" type="string"/>
  <sub name="mpihosts" description="Number of MPI Hosts"
       default="4" type="string"/>
  <sub name="workloadmax" description="Maximum allowable workload"
       default="-1" type="string"/>

Example 13. Sample Configuration File Stub

@MPIHOSTS ./MPImachines %mpihosts%