stampandsortFTP/VAN/Email maps

The stampandsortFTP, stampandsortVAN, and stampandsortEmail maps are identical with the exception of the communication protocol. The configuration requirements for these three maps are described here, using the stampandsortFTP map as a specific example.

The stampandsortFTP map is designed to retrieve data using the FTP protocol and to submit that data to the Message Manager. The stampandsortFTP map performs the following four tasks:

  • Gets data through the FTP resource adapter, using the FTP configuration information you supplied when you defined the FTP Get post office. An example FTP command line might be:
    
    -URL ftp://ediuser:password@192.1.1.50/receive.txt;type=i
    
  • Creates a unique ThreadID for the entire FTP transmission (the contents are concatenated as a single data stream if you use the FTP command MGET).
  • Archives the data retrieved through FTP in the install_dir\tmgr_vn.n\mmgr\archive\stampapp directory with an archive name adhering to the archive naming convention requirements.
  • Writes the data out to a file as install_dir\tmgr_vn.n\mmgr\stampec\*.mec. The * represents the valid ThreadID assigned to the FTP transmission.

As delivered with the Message Manager, the stampandsortFTP map is not configured to run by default. The stampandsortFTP map does not have time or input event triggers defined. The following procedure describes how to activate the stampandsortFTP map.

To activate the stampandsortFTP map

Note: The following procedures assume you have experience with Partner Manager and the Design Studio.
  1. Create an FTP Get post office in Partner Manager with a valid FTP command line.
    (Create post offices using the Partner Manager Post Office navigator. In this navigator window, click Add
    See the FTP Adapter documentation for information about valid FTP command lines.
  2. Open the msg_mgr.msd system in the Integration Flow Designer.
  3. Select the stampandsortFTP map component in the StampAndSort subsystem.
  4. Click the execution settings button on the stampandsortFTP map component to display the Launcher Settings window.
  5. For the TimeEvent setting, add a time event trigger by setting the TimeEvent Switch to ON and specifying the Trigger Interval settings.

    As discussed in the export map documentation, it is recommended that time events for FTP sessions be scheduled to start a few minutes after system startup to ensure the export process has completed before receiving data. You may also consider distributing FTP sessions over time if your systems are bandwidth-constrained.

  6. Modify the Input(s) information for the #1 POInfo input card.

    The GET source field for input card 1 (POInfo) of the stampandsort maps need to be updated with a string to indicate the Post Office nickname and the direction as follows -PON EDI -DIR i, where PON and DIR are keywords and are case-insensitive. The value for dir can be i (inbound), or o (outbound).

    Note: The three-character PO Nickname must match the nickname created in Partner Manager. The Message Manager uses this three-letter nickname to create a valid and unique ThreadID.