In an earlier quickstart guide to setting up an AS2 server, we featured a manual method for sending EDI messages. Because EDI transactions are best carried out automatically, we thought it would be a good idea to show you how to implement real-time transactions on the same solution we used in that post.
AS2 (applicability statement 2) uses public keys and private keys to encrypt files being transferred between IP addresses. With AS2, security, authentication, message integrity and privacy are ensured with encryption, digital certificates and nonrepudiation techniques. AS2 provides greater security for your EDI data than standard FTP, supporting synchronous and asynchronous MDN (message disposition notification) and digital signatures.
Plus, with JSCAPE's AS2 server you can send files regardless of file size and content type.
Would you prefer to watch a video version of this tutorial instead? You can play the video below. Otherwise, just continue reading.
Since this is a continuation of the previous article, click the link above to gather some context before continuing.
Ready? Let's get started.
There are many ways to automate AS2 file transfers on JSCAPE MFT Server. In this example, we're going to configure a Directory Monitor that captures inbound file additions and a trigger that responds to the Directory Monitor File Add event type.
A Directory Monitor allows you to capture events on local directories behind your firewall. For instance, a directory monitor can detect when a file is added, when a file is deleted, or when a file undergoes changes. The monitor we're about to create will be monitoring a directory for any new file additions.
This can be useful in cases where, as part of a business process process, an EDI document is placed into the monitored directory for transmission.
As soon as our server detects that a file has been added into the monitored directory, it will automatically grab that file and forward it to the designated trading partner through an AS2 connection.
Creating The Directory Monitor
It's now time to create the directory monitor in question. Go to the Directory Monitors menu and click the Add button.
Give the monitor a name, e.g. "DM for tp2as2". After, that, click the Browse button, navigate to the directory you want to monitor and select it. After you do that, the Directory field will then be populated with the path to that directory (e.g. C:\foruploads)
Note that the Monitor interval is set to 600 seconds. That means, the monitor will check the monitored directory every 600 seconds. You may adjust that value to meet your organization's needs.
Make sure the Monitor file add checkbox is ticked and then click OK. These settings will allow this directory monitor to fire a Directory Monitor File Added event once a newly added file is detected.
If you want that directory monitor to activate on a pre-set schedule, say, every 8:30 AM on the second day of each month or every night at 9:30 PM, you can also do that. Check out these posts later if you want to see how to implement those:
How To Get Your MFT Server To Email You About Last Night’s Download
After clicking OK, you should then see your newly created directory monitor in the Directory Monitors tab.
Creating The Trigger
We're now ready to create a trigger that would respond if a file is added to the monitored directory.
Go to the Triggers menu and then click the Add button.
Give the trigger a name (e.g. "upload to tp2as2") and then select the Directory Monitor File Added event type.
Click Next to proceed.
In a production environment, it's possible to have several directory monitors that throw the Directory Monitor File Added event type. To make this trigger act only on an event thrown by the directory monitor we created earlier, you can specify that monitor in the Trigger Conditions box like this:
MonitorName = "DM for tp2as2 uploads"
This is the name we assigned to our directory monitor.
MonitorName is just one of the many variables you can use in this context. To know which variables are available for a particular trigger, just click the Variables button found near the bottom-left of the screen.
Click Next to proceed.
In the succeeding screen, click the Add button to add a new Trigger Action. This will tell JSCAPE MFT Server what action this trigger should carry out in response to the Directory Monitor File Added event. Because we want it to forward the newly added EDI document file to an existing AS2 trading partner, select the Trading Partner File Upload action from the drop-down list. Click OK.
When the Trading Partner File Upload action parameters dialog appears, do the following:
- Select the trading partner from the Partner drop-down list (in our case, that would be "tp2as2", which was defined in the previous article).
- Enter the %File% variable (or click the Add Variable button and select File) into the Local File field. In this context, the %File% variable holds the complete path of the file that was added into the monitored directory. The variables supported by a particular trigger action depends on the trigger event used. To know which variables are supported, just click the Add Variable button.
- Click OK
Get Your Free Trial
Would you like to try this yourself? JSCAPE MFT Server is platform-agnostic and can be installed on Microsoft Windows, Linux, Mac OS X and Solaris, and can handle any file transfer protocol as well as multiple protocols from a single server. Additionally, JSCAPE enables you to handle any file type, including batch files and XML. Download your free 7-day trial of JSCAPE MFT Server now.