You can use external files to store job or order parameters.
This has the following advantages:

External files are specfied in the JobnScheduler Object Editor JOE using the "Parameter Includes" Tab. The following screen shot shows the parameters being specified for a job but the approach for an order is identical:

The above example generates the following configuration:

 <?xml version="1.0" encoding="iso-8859-1"?>
     <include live_file="my_parameter_file.xml" node=""/>

See for more information.

A typical parameter file would look like:

 <?xml version="1.0" encoding="iso-8859-1"?>
   <param name="param1" value="value1"/>
   <param name="param2" value="value2"/>
   <param name="param3" value="value3"/>
   <param name="param4" value="value4"/>

In this case you do not have to specifiy the node attribute.

You can also use a different structure.
In particular you can have multiple parameter sets:

 <?xml version="1.0" encoding="iso-8859-1"?>
   <database_connection id="myConnection1">
     <param name="host" value="myHost"/>
     <param name="port" value="myPort"/>
     <param name="user" value="myUser"/>
     <param name="password" value="myPassword"/>
   <database_connection id="myConnection2">
     <param name="host" value="otherHost"/>
     <param name="port" value="otherPort"/>
     <param name="user" value="otherUser"/>
     <param name="password" value="otherPassword"/>

In this case you must specify the node attribute with an Xpath expression.
If a job needs the parameters from myConnection1 then use e.g. //database_connection@id='myConnection1'/param.

It is recommended that you use the from Hot Folder flag in JOE and store the external parameter file either:

Changes to external parameter files located outside the Hot Folder (./config/live or ./config/cache resp.) will not be taken over by JobScheduler unless the job or order is changed or JobScheduler restarted.