Difference between revisions of "Middleware"
| Line 2: | Line 2: | ||
The middleware utility is a standalone application which can be used in conjunction with Commander4j and is designed to allow you to translate files to/from the commander4j standard xml format. When you install the software it comes with some example transformations and sample messages to illustrate how it can be used. | The middleware utility is a standalone application which can be used in conjunction with Commander4j and is designed to allow you to translate files to/from the commander4j standard xml format. When you install the software it comes with some example transformations and sample messages to illustrate how it can be used. | ||
| + | |||
| + | Within the install folder you will find a number of subdirectories, some of which are used for running sample message transformations. | ||
| + | |||
| + | To watch a sample message transformation you can copy a file from the .\samples\input\xx xxxx folder into the .\interface\input\xx xxxx folder. | ||
| + | |||
| + | Providing the interface has been started the sample file will be removed from the input folder and a new file will be created in the .\interface\output\xx xxxx folder. | ||
Revision as of 19:30, 6 January 2018
The middleware utility is a standalone application which can be used in conjunction with Commander4j and is designed to allow you to translate files to/from the commander4j standard xml format. When you install the software it comes with some example transformations and sample messages to illustrate how it can be used.
Within the install folder you will find a number of subdirectories, some of which are used for running sample message transformations.
To watch a sample message transformation you can copy a file from the .\samples\input\xx xxxx folder into the .\interface\input\xx xxxx folder.
Providing the interface has been started the sample file will be removed from the input folder and a new file will be created in the .\interface\output\xx xxxx folder.
