A Source activity enables you to specify the location from where you can fetch the data. The MFT Source activity allows you to fetch data from an MFT queue. This activity can either be triggered by an event or explicitly run. The following example depicts the explicit type of execution; however, you may refer to the Triggered by Event section to execute a process flow automatically based on GBI File Event.
To create an MFT SourceLogs enable you to trace the details of a particular request or a user's activity. Adeptia Suite maintains the logs of all the activities performed using Primeur Spazio MFT/s Server. The information includes the time stamp (date, start and end time, and time zone), type of event, outcome of the activity, its correlation ID, and other information.
To view Spazio logs:
...
- Go to Develop > Solutions > MFT Server > MFT Source.Click Create New.
- On the new MFT Source window, provide a unique MFT source name and description. Select the execution type - Run Explicitly or Triggered by Event.
- Expand Advanced Properties. For information about the fields, refer to Changing Advanced Properties.
- Click Save.
Run Explicitly: Select this option to execute the process flow manually by clicking the execute icon
on the Process Flow screen.Triggered by Event: Select this option to trigger the process flow through an MFT File event. In this case, you need to create an MFT File event and bind this event with the source activity in the process flow.
Based on the option chosen in the previous step, the list of fields differ.
For Run Explicitly
| Field Name | Description |
|---|---|
| Queue Manager | Name of the Queue Manager from where you want to fetch the data. |
| Queue | Name of the MFT queue mentioned in the Queue Manager. |
| User Class | Name of the MFT user class. |
| Sender Name | Name of MFT sender. The sender in this context is a logical MFT level sender identifier (not the actual userid/subject in AuthN/AuthZ terms) and can be used for filtering. |
| Correlation Id | Name of MFT correlation identifier. Correlation identifier is a logical tag that can be associated with MFT files having some business level affinity (for example, "PAYROLL.FILES") and can be used for filtering. |
| Include Consulted | Set the value to true to read the file multiple times. |
| User Id | MFT connection user id. |
| Password | MFT connection password. |
| Disposition | Whether to keep the file or remove it after successful execution. Keep: Retain the file on the input queue after successful execution. Remove: Remove the processed file from the input queue. |
| External File Attributes | Optional extended metadata elements that can be attached to a file (very similar in nature and purpose with JMS message selectors). The value for this attribute can also be set explicitly in the process flow context. |
| Field Name | Description |
|---|---|
| User Id | MFT connection user id. |
| Password | MFT connection password. |
| Disposition | Whether to keep the file or remove it after successful execution. Keep: Retain the file on the input queue after successful execution. Remove: Remove the processed file from the input queue. |
| External File Attributes | Optional extended metadata elements that can be attached to a file (very similar in nature and purpose with JMS message selectors). The value for this attribute can also be set explicitly in the process flow context. |
- Primeur Spazio MFT/s > Spazio Logs.
- By default, the system displays current day logs. These log entries are grouped according to their correlation ids. To view all the entries of a particular correlation key, expand the group by clicking the plus icon (
).
- You can also use Advanced Search option (
) to view the logs of a particular time interval. 
To view AS2 Logs, go to Develop > History > AS2 Logs.
