Difference between revisions of "Middleware"

From Commander4j Wiki
Jump to: navigation, search
Line 1: Line 1:
 
[[File:C4jMiddleware.gif]]
 
[[File:C4jMiddleware.gif]]
  
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 on its own or in conjunction with Commander4j. It is designed to allow you to translate files between different formats/structures. 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.
+
For example you can convert a CSV into and XML, and XML into a Plain ASCII file. A CSV into an Excel  file and many many other scenarios.
 +
 
 +
Within the install folder you will find a number of subdirectories, some of which are used for running sample message transformations. Look at the list of sample transformations and use the same files to see what they do. You can then edit the configuration to create your own transformation.
  
 
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.
 
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.
 
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.
 +
 +
The user interface shown above is for testing and development purposes. In a production environment the application would run as a background service. The software can be configured to generate emails if an error condition occurs.
  
 
The sample [[middleware  config.xml|config.xml]] which can be found in the ./xml/config directory contains a number of example transformations.
 
The sample [[middleware  config.xml|config.xml]] which can be found in the ./xml/config directory contains a number of example transformations.
  
* [[map01]] - Rockwell Material Master to C4J Material Master
+
* [[map01]] - NES Konnect XML Material to C4J Material Master. Transforms and XML containing material data into a different structure suitable for importing into Commander4j.
* [[map02]] - S95 Process Order to C4J Process Order
+
* [[map02]] - NES B2MML S95 XML Process Order to C4J Process Order. Translates a B2MML S95 structured XML document into a format suitable for Commander4j.
 
* [[map03]] - Synchro CSV
 
* [[map03]] - Synchro CSV
 
* [[map04]] - S95 Batch Status Change to C4J Batch Status Change
 
* [[map04]] - S95 Batch Status Change to C4J Batch Status Change

Revision as of 15:19, 9 May 2019

C4jMiddleware.gif

The middleware utility is a standalone application which can be used on its own or in conjunction with Commander4j. It is designed to allow you to translate files between different formats/structures. When you install the software it comes with some example transformations and sample messages to illustrate how it can be used.

For example you can convert a CSV into and XML, and XML into a Plain ASCII file. A CSV into an Excel file and many many other scenarios.

Within the install folder you will find a number of subdirectories, some of which are used for running sample message transformations. Look at the list of sample transformations and use the same files to see what they do. You can then edit the configuration to create your own transformation.

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.

The user interface shown above is for testing and development purposes. In a production environment the application would run as a background service. The software can be configured to generate emails if an error condition occurs.

The sample config.xml which can be found in the ./xml/config directory contains a number of example transformations.

  • map01 - NES Konnect XML Material to C4J Material Master. Transforms and XML containing material data into a different structure suitable for importing into Commander4j.
  • map02 - NES B2MML S95 XML Process Order to C4J Process Order. Translates a B2MML S95 structured XML document into a format suitable for Commander4j.
  • map03 - Synchro CSV
  • map04 - S95 Batch Status Change to C4J Batch Status Change
  • map05 - S95 Transfer Schedule to C4J Pallet Status Change
  • map06 - S95 Process Order Status Change to C4J Process Order Status Change
  • map07 - C4J Production Declaration to S95 Production Declaration
  • map08 - ASCII Flat File Fixed Column to XML
  • map09 - Tropos Material XML
  • map10 - Tropos Works Order XML
  • map11 - C4J Production Declaration to TROPOS Goods Receipt
  • map12 - C4J Production Declaration to ASCII Flat File
  • map13 - C4J Production Dec to ASCII and CSV Files
  • map14 - W-ware FFMW Material to C4J MM
  • map15 - C4J Equipment Tracking to ASCII Flat File
  • map16 - Split inbound XML into 2 outbounds
  • map17 - Excel Spreadsheet
  • map18 - SAP Idoc Material Master to C4J XML