Task: define an application subsystem

Edit online

About this task

In this task you will define an application subsystem to take the inbound purchase order and transform it so it can be processed by your internal purchasing application.

Use the EDI850IN.mms map to convert the data in the subsystem. You want this map to execute based on the arrival of data in the Put Post Office directory that you defined for Acme Corp. with an extension of *.app

Procedure

  1. Start the Integration Flow Designer and open a new system definition file.
  2. Save the new system definition file in C:\install_dir\tmgr_vn.n\tutorial\exercises\myfiles as AppMap.
  3. Rename System1 to Inbound.
  4. Add the map in the EDI850IN.mms source map to the Inbound system.
  5. Right click on the EDI850IN map in the Inbound system and select Edit Launcher Settings to set the input trigger and override the source and destination file paths as follows:
    • Input card
      Source Event is On
      Source file: C:\install_dir\tmgr_vn.n\tutorial\exercises\myfiles\in
      \app850in\*.app
    • Output card #1
      Target file: C:\install_dir\tutorial\exercises\myfiles\in\app850in\*.ord
    • Output card #2
      Target file: C:\install_dir\tmgr_vn.n\tutorial\exercises\myfiles\in\app850in\*.lin
  6. Change the from the Server drop-down list to Local Server.
  7. Create a deploy script named as Inbound with C:\install_dir\systems directory as the deploy directory.

    Note: Select option Build and Transfer Maps as well.

  8. Deploy the Inbound system.
  9. Save the changes to the system definition file.
  10. Verify that all *.app files were deleted from the directory:

Results

C:\install_dir\tmgr_vn.n\tutorial\exercises\MyFiles\In\app850in