▪ The refKColl tag references a collection of data defined in this self-defined processor file.
▪ The refFormat tag named firstFormat references a format defined in this self-defined processor file
▪ The refFormat tags named secondFormat and thirdFormat reference formats that are not defined here. The toolkit formats definition file must therefore define these formats.
▪ The refService tag references a service defined in the self-defined processor file
▪ Data5 is not defined in the self-defined processor file. The toolkit data definition file must therefore define this data.
▪ The workstation context is not defined here. The toolkit context definition file must therefore define this context.
2 In the toolkit configuration (dse.ini) file, check that the value of the modularity field is appropriate.
This field allows the toolkit to distinguish between self-defined and regular processors.
<field id="modularity" value="modularityType" />
Where modularityType can be:
▪ grouped - The toolkit only uses entities defined in the toolkit definition files. This is the default value.
▪ split - The toolkit only uses entities defined in self-defined files.
▪ mixed - The toolkit uses regular and self-defined entities.
3 To enable externalizers to find the definitions, do one of the following ways:
▪ Specify the path and file name of the self-defined processor file inside the files.processors keyed collection:
▪ The value of the id attribute is the name of one self-defined processor.
▪ The value of the value attribute is the name of the file containing the self-defined processor definition. This attribute is optional and if not defined, the toolkit searches for a file with the name of the self-defined processor with a .xml extension.
▪ The value of the path attribute specifies the location of the self-defined processor file. This attribute is optional and if unspecified, the toolkit uses the value of the generic path in the paths collection to search for the file. See the following bullet for a description of the generic path.
The following example contains many ways of defining the location of the self-defined processors. See the notes below the example for the effect of defining the tag in its way.
[c] Uses the default file name and the generic path.
[d] Reads the file from an HTTP address.
[e] Reads the file from a .zip file.
[f] Reads the file from a .jar file.
▪ Place the self-defined file in the generic entities path. The definition of the generic path is in the paths keyed collection. The toolkit uses the generic path if it cannot find the location of the file in the processors section of the files keyed collection. If the file does not contain generic entities path definition, add its definition:
▪ The path to the definition files for the toolkit entities such as operations, processors, data, and formats. The path can be an absolute path or relative local path from the location of the toolkit configuration (dse.ini) file.
▪ The HTTP address of the definition files. It can be an absolute path or a relative path from the location of the toolkit configuration (dse.ini) file.
▪ The value "fromJar". The toolkit reads the entities from a JAR file.