Skip to main content
Eptura Knowledge Center

Local File Repository

  1. Last updated
  2. Save as PDF

Level: Eptura Implementation team / Client IT team

This describes the install process for the local file repository used with job ticket attachments. 

Contents

This functionality requires a Microsoft IIS server and the process involves installing an ISAPI plug-in called Tabs Upload and creating a URL for use with a set of ASP pages. Eptura Workplace supports all serviceable versions of Windows Server and our Eptura Professional Services team will work with you to enable the local file repository.

clipboard_ee2e034d94389c08075eed3a0f2788085.png

 

Installation

Prerequisites

  • CPU requirements are minimal (1 GHz for x86 processors or 1.4 GHz for x64 processors), and the memory requirements do not exceed 10 GB (able to run IIS and execute ASP pages). Disk space varies by customer (depends on documents and retention period). The application works in a shared environment and on a virtualized machine (VM).
  • In Windows server versions where "ASP Classic" is an option (such as Windows server 2003, 32 or 64 bit), "ASP Classic" must be enabled in IIS. In Windows server 2008, the “ASP” role under IIS must be enabled.

Step 1. Set up the File Upload Component (Client team)

  1. Install Microsoft IIS.
  2. Enable ASP Classic / ASP. https://www.iis.net/learn/application...default-on-iis
  3. Download the Tabs software at: http://downloads.iofficecorp.com/servlet/servlet.FileDownload?file=015A0000001CH5Z

The zip file contains an asp folder and a bin folder.

clipboard_ea9b71531c54510cb994c792da8a2708b.png

clipboard_ed95ea399e4ae0e953f167ad782c89da7.png

  1. Run the appropriate Tabs Upload installer (either x64 for 64-bit Windows, x86 for 32-bit) and contact Eptura Workplace to receive your Tabs Upload license key.
  2. Create a new website or virtual directory in IIS.
  3. Move the contents of the ‘asp’ folder to the website's home directory. The URL to this IIS site is called the website URL.
  4. Create a folder on the server. IIS must have the appropriate security rights to read and write to this folder. This folder is called the storage directory.

Step 2. Provide Information Exchange to Eptura (Client Team)

  1. Provide the internal website URL to Eptura and this can be either the local IP address or the DNS name. Our Professional Services team uses this in Eptura Workplace to direct the user's browser to the repository.
  2. Provide the storage directory to Eptura and this is used to direct the Tabs Upload application to store the files in the directory.

Security

  • Internet Explorer - To access your URL from certain versions of Internet Explorer, the website must first be added to the Trusted sites list using the Internet Options window.
  • Google Chrome - If you are using Google Chrome to access your URL, an SSL certificate is required and the website must be a secured (https://) site.

Step 3. Test the Local File Repository working with the Copy Module (Client Team)

Make sure you verify the Local File Repository is working.

  1. Open up the web browser and head to the website URL. For example, https://internalserver/form.asp. If the website is set up correctly, the customer will see a simple file upload form.
  2. Log into the application.
  3. Navigate to the Copy module.
  4. Create a new copy ticket, upload a file, and submit the copy ticket.
  5. Log into the server, verify that the file was transferred to the storage directory successfully.

Troubleshooting

Below are the troubleshooting items to help you quickly diagnose issues.

Situation Resolution

Local file repository did not return any files.

 

This can happen when an HTTP local file repository tries to HTTP POST data to an HTTPS site.

If the file is not in the storage directory, verify permissions on the folder and in IIS. Make sure appropriate permissions (read/write) have been set for the IIS account.

Verify the website URL forwarded to Eptura. Check the server address, virtual site name, and full path. 

Local file repository did not return any files.

 

This can happen if an HTTP local file repository tries to HTTP POST data to an HTTPS site.

If an ASP error is received, "Cannot create a temporary file in the upload folder. Access is denied."

clipboard_e2ed01630184697d8fa3974aea948d9b5.png

IIS must have the appropriate security rights to read and write to the server folder (storage directory).