IntegrationsIntegrate by File Drop

File Drop integration extends the functionality of other applications so users can print labels generated with data provided by those applications. A print job is initiated by placing a print job file into a folder that Loftware Enterprise SP monitors.

To create a File Drop integration that allows print job files to be processed by Loftware Enterprise SP, do the following.

  1. In Integrations Integrations, in the ribbon click > File Drop to create a new File Drop integration.
  2. In the General panel, configure the following details about print request files.
    1. A different job target folder must be configured for each integration. For Job Target Folder, select a unique folder in Loftware Enterprise SP to which status information about print jobs related to this integration should be directed.
    2. For Default Process, select either a process that you have created that should be applied to the integration, or else select the Generic Document Process in the root folder.
    3. For Transaction Size, enter the number of labels to allow in a batch. It is recommended to set this value to be greater than the size of any expected batch of print job details you may need to send. For example, if you have a stacked job with 200 labels being printed to the same device, the transaction size should be set to 201 or greater.
    4. For Run As, select the Loftware Enterprise SP user account under which print job files associated with this integration should be processed. This user account must have at least the INTEGRATOR role or equivalent permissions.
  3. In the Advanced panel, configure the following details.
    1. For Scan Folder, enter a UNC path to a shared folder or a path to a local folder on the Loftware Application Server to which print request files will be dropped. For example, \\Server01\ScanFolder or C:\ScanFolder. If the folder does not exist, it is created.

      Important! For best performance, it is recommended that each Scan Folder be associated with only one integration so that integrations do not scan the same job files.

      WARNING: Files should not be edited in the Scan Folder. Editing a file in this folder may strand the associated print job. If FIFO is selected and a job file in the Scan Folder is being edited, then when Loftware Enterprise SP encounters that job file in the queue Loftware Enterprise SP is blocked from continuing to process any job files using the same integration.

    2. For File Type Extension, select which file types this integration should process and by what file extension each selected file type is identified. You must specify a file extension for any file type selected. Do not include a period in the file extension. A file type can be associated with only one file extension in an integration. If you select XML Transform, you must provide the path to the stylesheet in the Specify Stylesheet field.
    3. For Polling Interval, enter how frequently in milliseconds (ms) Loftware Enterprise SP should check the Scan Folder for new print job files.
    4. You can restrict the order in which incoming jobs are processed.
      • To allow the order in which incoming print job files are processed to vary and to ensure that a blocked job does not block all jobs that follow it, clear FIFO.
      • To require incoming print job files to be processed in the order in which they are created, select FIFO.
    5. To ensure that the XML produced is properly formatted, it is recommended that you select Validate XML.
    6. Each print job file specifies the device or devices to which the job will be sent.
      • To send each job to the device or devices specified in the job, leave this field blank.
      • To override that device selection and send all jobs that use this integration to a particular device, enter a Device Name.
    7. If migrating from a Loftware Print Server (LPS) environment that includes more than one LPS, for Legacy LPS Name enter the PRINTERNUMBER for the LPS.
  4. In the Archive Options panel, it is recommended that you clear Archive Original Job File and Archive XML check boxes except during testing.
  5. In the Properties pane, enter a description of the purpose of the integration.
  6. Click File > Save or click Save Save in the toolbar.
    1. In the Save dialog box, enter a name for the integration.

    2. In the left pane of the Save dialog box, select the folder in which to save the integration. You can click a folder to display subfolders.
    3. Click OK to save the integration. Creation information is displayed in the Properties pane.
  7. In the ribbon, click HomeStart Integration.
  8. To verify that the integration has started, view the Status in the Properties pane.

Important! Whenever you add a new device, data service, integration, or facility, you must ensure that the service is activated on all Loftware Application Servers on which it should be available to run and started on at least one. In an environment with only one Loftware Application Server, these types of services are automatically activated and started when they are created. For more information, see High Availability with Distributed Services.