The COBOL sample contains three DFDL message models and sample binary data for each.
How to run the OrderList to PurchaseData scenario
In this scenario, the message flow "OrderList2PurchaseData" is transforming one COBOL message to another. The input COBOL message is defined by the
COBOL copybook "OrderList" and the message model that is contained in the DFDL schema file, "OrderList". The output COBOL message is defined by the
COBOL copybook "PurchaseData" and the message model that is contained in the DFDL schema file, "PurchaseData".
In the Application Development view, ensure that your resources are viewed as projects,
expand COBOLApplication > Flow Tests,
and double-click COBOLApplication.mbtest to open it in the Test Client.
In the Test Client, under Message Flow Test Events,
select Invoke Message Flow(COBOL OrderList to COBOL PurchaseData)
or Invoke Message Flow(XML OrderList to COBOL PurchaseData).
Click the Start icon.
A message is sent through the Binary2Binary message flow.
When the test is complete, the returned message will be displayed.
Select Show Hexadecimal viewer to see the hex values of the returned binary data.
Note that the received message was serialised using the PurchaseData model.
How to run the CustomerAddress scenario
In this scenario, the message flow "Redefine" is transforming a COBOL message into an XML message with the same logical structure. The input COBOL message is defined by the
COBOL copybook "CustomerAddress" and by the message model that is contained in the DFDL schema file "CustomerAddress".
The message flow copies the logical tree structure from the input COBOL message, parsed in the DFDL domain, to a XMLNSC Domain for serialization as an output XML message.
In the Application Development view, ensure that your resources are viewed as projects,
expand COBOLApplication > Flow Tests,
and double-click COBOLApplication.mbtest to open it in the Test Client.
In the Test Client, under Message Flow Test Events,
select Invoke Message Flow(COBOL Address to XML).
Click the Start icon. A message is sent through the Redefine message flow.
When the test is complete, the returned message will be displayed as XML in the Test Client.