PoC Installation iFinder

Server

• Windows Server 2016 or higher
• The iFinder server must be connected to the domain
• To access the search interface, the clients need access to the iFinder server at http://[server name]/iFinder/. To access the iFinder frontend via a secure URL, a signed certificate for the server must be available. In this case the search interface is reached via https://[server name]/iFinder (server name is either IP, host name or FQDN).
• SSL web server certificates for end user access must be provided by the customer for the corresponding hostnames or FQDNs (IP addresses are not suitable for SSL encryption see RFC1918 and RFC6598). Optimally as PFX files (or comparable, directly processable by Apache Tomcat) including root and intermediate certificates.
• In an installation, end users need access to the iFinder UI via IP, hostname or FQDN using port 80 (or 443 if an SSL certificate is provided). Optionally also via port 9680 if administrators should have access to the admin interface.

Sizing

• Please note that we need a dedicated meeting to negotiate a sizing for your PoC. Every PoC has specific requirements and we need to address them. Do not order any resources or hardware before talking to us!
• Example: For a usual PoC with up to 1 million documents to index and only a few concurrent users we suggest a server with 8 cores, 32 GB RAM, 50 GB free space on the harddrive for the installation (e.g. C:\Intrafind) and 150 GB available space on another harddrive (e.g. E:\Index) for the index data. If possible you should use SSD for the index data because of performance reasons.
  You could also use spinning drives (HDD) but if you focus on index times and response times we strongly recommend SSD to get optimized results.

iFinder

• The installer contains all necessary components (like Java, Webserver, etc.)
• Java should not be preinstalled on the server
• You need a local administrator account for the installation process (installing services)
• You need a user with at least read access to all data on the fileshare which has to be indexed, write permissions to the installation directory (e.g. C:\Intrafind) and the „log on as a service“ permission on the installation server
• To consider the access rights while searching you need a user with LDAP read access (a simple domain user is eligible by default)

Access rights

• It would be helpful to create a dedicated AD user group for testing. You need at least the names of the AD user groups (e.g. DOM\groupname) which will use the iFinder frontend
• We recommend to create a dedicated user group for the administrators
• You need the full hostname or the FQHN of the domain controller
• You need the LDAP(S) Server URL like ldap://ad-domain.firma.de:3268.

Indexing

• The directories to be indexed must be present as UNC paths (e.g. \Server\path\).
• If an anti-virus software is present, please exclude the installation directory (default: C:\Intrafind) because of performance reasons
• The index can optionally be swapped to a separate drive (e.g. E:\Index). The virus scanner should not monitor this directory either.
• The server needs access to the LDAP(S) servers (ports for Global Catalog, usually 3268 (LDAP) and 3269 (LDAPS)) and to the sources.

Access to the server

• Optional: Install the current version of TeamViewer (e.g. Quick Support) on the iFinder server (http://www.teamviewer.com/en/download/windows.aspx)
• As a workaround install Teamviewer on a client computer to use this as a proxy for accessing the server controlled by you

Miscellaneous

• A few days before the installation you will receive a download link to download all installation files to the server (~ 2.5 GB filesize)
• You will get the license file in a separate email. Please copy this license file to the server.

If you want to connect other sources (like Office 365, Confluence, Jira, databases, ...) in your PoC we must discuss the prerequisites for every connector separately to consider the sizing requirements.