Total Management Technical Requirements
Ver si on 6 .0
Copyright Intapp, Inc. All rights reserved.
T ABLE
OF
C ONTENTS
Preface
4
Purpose of this Guide
4
Who Should Use This Guide
4
Disclaimer
4
Intapp Web Site
4
Intapp Technical Support
4
Intapp Customer Portal
4
Intapp Product Feedback
4
Time Management
5
Database Server
5
Stand-alone SSRS Administrative Reports Server [optional]
6
Time Management Server (IIS)
6
Capture Server (IIS)
6
Dedicated Intapp Integration Platform
7
Time Management Desktop
7
eBillingHub Integration
8
Time Capture Desktop Extension (DE)
8
Microsoft Exchange Integration
9
DMS Integration
9
Billing System Integration
10
Phone System Integration
10
Digital Dictation Integration
10
Server Configuration Considerations
10
Time Entry 2012/2013/2014: Minimum Recommended Requirements
12
Intapp Integration Platform
12
Administrative Reports Server Requirements
12
Workstation Requirements
12
eBillingHub Integration
12
Intapp Time Mobile for iOS
13
Intapp Time Mobile for Good Technology
13
Intapp Time Mobile for Android
13
Intapp Time Mobile for BlackBerry
13
Time Capture
Database Server
Page 2
14
14
Intapp Time™: Technical Requirements
Presentation Web Server (IIS)
14
Mobile Web Server (IIS)
15
Intapp Integration Platform
15
Time Capture Desktop Extension (DE)
16
Time Capture Timers
17
Time Capture BlackBerry Extension
17
Time Capture Carrier Capture
17
Microsoft Exchange Integration
18
DMS Integration
18
Billing System Integration
18
Time Entry System Integration
19
Phone System Integration
19
Digital Dictation Integration
19
Peak Load Estimates
19
Peak Load Tests
20
Server Configuration Considerations
20
Intapp Time™: Technical Requirements
Page 3
P REFACE
Purpose of this Guide
The purpose of this document is to detail the Intapp Time Technical Requirements.
Who Should Use This Guide
This guide is for Administrators and Implementers, program managers, and implementation partners, including
those who will conduct training with the Intapp Time application.
Disclaimer
This document is the property of Intapp, Inc., and is delivered to customers and partners. Although all efforts have
been made to keep this document up to date, all content is subject to change as new versions of the Intapp software are released. This document may not be distributed to persons, companies, or entities other than the intended
recipients without the consent of Intapp, Inc.
Note: SQL Express Edition is not supported.
Intapp Web Site
You can access the Intapp corporate web site at www.Intapp.com. The site contains information about Intapp, its
background, upcoming events, and sales offices. You will also find product and partner information. The services
area of the site includes important information about technical support, training and education, and implementation services.
Intapp Technical Support
For questions regarding Intapp Time or any Intapp product, please contact Intapp Technical Support at
855.470.0705 (800.011.3446 in the United Kingdom), or send an email to [email protected].
Intapp Customer Portal
For updates on Intapp Time or any Intapp products, visit our Customer Portal at Intapp.force.com/portal/.
Intapp Product Feedback
Your feedback is important and helps us to improve our products. Please submit your suggestions or ideas on our
Customer Portal at Intapp.force.com/portal/.
Page 4
Intapp Time™: Technical Requirements
T IME M ANAGEMENT
Database Server
l
Microsoft SQL Server: For Time Management, Time Entry and Capture each require a separate database on a
Microsoft SQL Server. Although Microsoft and Intapp recommend separate servers for each application, one
SQL server can be used for both applications if desired (increases in RAM and CPU may need to be made).
Supported versions include:
n
Microsoft SQL Server 2014
n
Microsoft SQL Server 2012
n
Microsoft SQL Server 2008 R2
n
SQL Server Edition: Standard or Enterprise
Note: SQL Express Edition is not supported.
l
Collation type: The database must use collation type SQL_Latin1_General_CP1_CI_AS or SQL_Latin1_General_CI_
l
AS.
l
Security:
n
The Time Capture database requires a user name and password (either SQL or Windows) that has privileges to connect and create a new database, tables, and other objects. n
The Time Entry database requires a SQL login.
Minimum System Recommendations:
For Average Size Installs < 1000 Timekeepers
n
4x 2.0 GHz CPU with 1MB cache, or equivalent
n
8 GB RAM (16 GB if Time Entry Reporting is also installed with SSRS on the same box)
n
154 MB disk space per user per year
n
Windows Server 2012, 2008 or 2003
For Larger Installs > 1000 Timekeepers
n
8x 2.0 GHz CPU with 1MB cache, or equivalent
n
16 GB RAM (32 GB if Time Entry Reporting is also installed with SSRS on the same box)
n
154 MB disk space per user per year
n
Windows Server 2012, 2008 or 2003
Load Requirements: For a 1000-attorney law firm and Time Capture, Intapp recommends a SQL Server that can
handle the following:
n
Database size of 8-10 million rows when in full production
n
Transaction load of 150,000 to 250,000 events per weekday in full production
Intapp Time™: Technical Requirements
Page 5
Stand-alone SSRS Administrative Reports Server [optional]
Minimum System Recommendations:
n
Microsoft SQL Server 2014
n
Microsoft SQL Server 2012
n
Microsoft SQL Server 2008 R2
n
8x 2.0 GHz CPU with 1MB cache, or equivalent
n
16 GB RAM
Time Management Server (IIS)
Note: If an optional DMZ configuration is chosen for mobile, an additional server would be required matching the
specifications below.
l
Microsoft IIS Server: The Time Management web applications must be installed on a Microsoft Windows
Server computer running Internet Information Services (IIS). Supported versions include:
n
Windows Server 2008 & (R2), 2012 & (R2), (IIS version 7, 7.5, 8.0, 8.5), 32-bit or 64-bit
l
The IIS server must have .NET Framework 2.0 plus 4 or later installed
l
ASP.NET 4.0: Once the .NET Framework has been installed, ensure that this version of the framework is the
one being used by IIS. This is done by selecting the web server's properties in the IIS administration console,
selecting the ASP.NET tab, and choosing ASP.NET version 4.0 from the dropdown.
l
Microsoft MVC 3.0
Note: Microsoft MVC 4.0 is not compatible at this time.
For Average Size Installs < 1000 Timekeepers
n
4x 2.0 GHz CPU with 1MB cache, or equivalent
n
8 GB RAM
n
60 GB disk space For Larger Installs > 1000 Timekeepers
n
8x 2.0 GHz CPU with 1MB cache, or equivalent
n
16 GB RAM
n
80 GB disk space
n
Cluster/NLB (Minimal recommendations are per node)
Note: The Time Management server is Cluster, VMware & Hyper-V server compatible.
Database Server and Time Management servers are expected to be on separate virtual or physical servers.
Capture Server (IIS)
l
Page 6
Microsoft IIS Server: The Capture web application must be installed on a Microsoft Windows Server computer
running Internet Information Services (IIS). Supported versions include:
n
Windows Server 2008 & (R2), 2012 & (R2), (IIS version 7, 7.5, 8.0, 8.5), 32-bit or 64-bit
n
Windows Server 2003 (IIS version 6)/2003 R2, 32-bit or 64-bit
Intapp Time™: Technical Requirements
l
.NET Framework 4.0: The IIS server must have .NET Framework 4 or later installed.
l
ASP.NET 4.0: Once the .NET Framework has been installed, ensure that this version of the framework is the
one being used by IIS. This is done by selecting the web server's properties in the IIS administration console, selecting the ASP.NET tab, and choosing ASP.NET version 4.0 from the dropdown.
l
(Windows 2003) Enable IIS Web Service Extensions: If the IIS server is Windows 2003, there may be additional steps required to enable ASP.NET pages to run. See the following articles from Microsoft support:
l
http://support.microsoft.com/kb/315122 and http://support.microsoft.com/kb/332124.
l
Time Capture database connectivity: The IIS server must be able to connect to the database server hosting
the Time Capture database.
l
Unicode Font support: Time Capture supports Unicode (multi-byte character sets). For the journal reports to
display Unicode properly, the font Arial Unicode MS (ARIALUNI.TTF) must be installed on the IIS server. For
users to be able to view Unicode in reports and the web application, this font must also be installed on the
user’s desktop PC.
Minimum System Recommendations:
l
n
4x 2.0 GHz CPU with 1MB cache, or equivalent
n
6 GB RAM
n
30 GB disk space
Latency: Users accessing the Time Capture Web Server should have latency under 200ms.
Dedicated Intapp Integration Platform
Intapp Integration Platform: The Intapp Integration Platform to be installed where it can make network connections to all
necessary source systems, including the Timevault database and all activity source systems. Due to the load of the integrations, The Time rules should be placed on its own dedicated Intapp Integration Platform separate from other Integration
Builder or Wall Builder processes.
Virtual Infrastructure:The Integration Platform is supported on the following virtualization software:
n
VMware ESXi
n
VMware ESX 3.5 + (Server or Cluster)
n
Microsoft Hyper-V 2008 R2+
Minimum System Requirements for the Virtual Image:
n
2x 2.0 Ghz CPU
n
4 GB RAM
n
55 GB disk space
Version: Intapp Integration Platform version 4.7.4 or greater is required.
Time Management Desktop
l
Windows: The Time Management Desktop client software must be installed on a Microsoft Windows XP,
Vista, Windows 7, Windows 8 or Windows 8.1 computer. Time Capture Desktop Extension (DE) supports both
32-bit and 64-bit operating systems.
l
.NET Framework 3.5 SP1: The Windows computer must have the .NET Framework 3.5 SP1 installed, the .NET
Intapp Time™: Technical Requirements
Page 7
l
Framework 3.5 SP1 download page has additional requirements to address known compatibility issues with
.NET Framework 3.5 SP1. If you have installed .NET SP1, please be sure that you have also installed the
appropriate KB updates as referenced on the. NET Framework 3.5 SP1 download page.
l
TCP/IP Networking
l
2GB RAM minimum, 4GB recommended with Windows 7 or higher
l
100 MB of disk space
l
VGA 1024x768
l
Citrix: Citrix servers require an average of 250-500 MB of memory per concurrent user.
eBillingHub Integration
Integration with eBillingHub requires that both the Time Management server and client software are running a minimum version of 2013.4.1.
Time Capture Desktop Extension (DE)
l
Windows: The Time Capture Desktop Extension (DE) client software must be installed on a Microsoft Windows XP, Vista, Windows 7, Windows 8 or Windows 8.1 computer. DE supports both 32-bit and 64-bit operating systems.
l
Web Server Connectivity: DE must be able to connect to the Time Capture web application.
l
.NET Framework 2.0: The Windows computer must have .Net Framework 2.0 installed.
Note: If you install the .NET Framework 3.5 SP1, the .NET Framework 3.5 SP1 download page has additional requirements to address known compatibility issues with .NET Framework 3.5 SP1. If you have installed .NET SP1, please
be sure that you have also installed the appropriate KB updates as referenced on the. NET Framework 3.5 SP1 download page.
Desktop Applications:
n
Default applications: DE contains built-in logic to obtain detailed usage information for the following
applications:
n
Microsoft Word 2013 (32-bit & 64-bit), 2010 (32-bit & 64-bit), 2007 (SP1 or above), 2003 (SP2 or
above)
n
Microsoft Outlook 2013 (32-bit only), 2010 (32-bit), 2007 (SP1 or above) or 2003 (SP2 or above)
Note: Outlook 2013 64-bit and Outlook 2010 64-bit are not supported at this time.
n
Microsoft Excel 2013 (32-bit & 64-bit), 2010 (32-bit & 64-bit), 2007 (SP1 or above) or 2003 (SP2 or
above)
n
Internet Explorer: Time Capture officially supports Internet Explorer 8 through 11
n
Adobe Acrobat Standard/Professional XI, X, 9, 8, or 7
n
Adobe Reader XI, X, 9 or 8
Note: DE has been tested only with the specific versions of the applications listed above. Using DE with older
versions of the applications listed above is not supported.
Custom Applications: DE can be configured to track usage of other Win32 applications. This is accomplished by
monitoring a specific process name. For custom applications, DE can also use the application’s window title to
track usage by the information contained in the window title.
For example:
Page 8
Intapp Time™: Technical Requirements
n
DE can be configured to track Microsoft PowerPoint by enabling monitoring of POWERPNT.EXE.
Since PowerPoint displays the document name in the window title, DE can track usage of each individual document being worked on in PowerPoint.
n
DE can be configured to monitor usage of Microsoft SQL Server Management Studio by enabling
monitoring of ssms.exe. The window title tracking functionality of DE does not provide any additional information since the window title only contains Microsoft SQL Server Management Studio
regardless of what action is being performed within the application. In this case, since no additional
usage context is available in the window title, DE will only be able to track the total time spent in SQL
Server Management Studio.
n
DE can be configured to track Yahoo Messenger by enabling monitoring of YahooMessenger.exe.
n
Since Yahoo Messenger displays the name of the person you are chatting with in the Window title, DE
can track usage of each individual person an IM conversation is occurring with.
l
Memory Usage: DE memory use will vary depending on the number of applications enabled to be tracked as
well as the number of simultaneous items being tracked. DE will use approximately 15-75MB of RAM on average. When DE is used in a Citrix or Terminal Server environment, you should expect DE to use 15-75MB of
RAM for each remote user. A portion of the RAM used by DE (typically 15-25MB) can be, and is often, shared
by other processes.
l
Citrix: DE can track application usage when DE is installed in a Citrix server environment that is configured
to use published desktops or published applications. To use DE in a published desktop environment, you
simply install DE on the Citrix server. A separate instance of DE will run for each remote desktop user. No
other configuration is needed for published desktops. To use DE for published applications, additional configuration is required as outlined in the Implementation Guide. DE is not currently able to track applications
that are configured as streamed applications.
l
Virtual Desktops DE can track most applications running in virtual desktop environments the same as if they
were running on a physical desktop by simply installing DE as part of the virtual desktop image.
Microsoft Exchange Integration
Time Capture uses the Exchange server to retrieve contact and calendar appointments, for the QuickNote feature,
and iPhone/iPad/Android sent email activity capture. Time Capture has been tested to support the following versions:
l
Microsoft Exchange Server 2013
l
Microsoft Exchange Server 2010
l
Microsoft Exchange Server 2007
l
Microsoft Exchange Server 2003*
*Certain features of the Time Capture component require Exchange Web Services which is not supported in
Exchange 2003. The Time Capture QuickNote feature and capturing iPhone/iPad/Android sent email activity is not
possible with Exchange 2003.
DMS Integration
Time Capture has been tested to support using the DMS database to retrieve the client/matter assigned to a particular document for the following document management systems:
l
Autonomy WorkSite 9.x, 8.x
l
Microsoft SharePoint 2010/2007
l
NetDocuments
l
Open Text/Hummingbird eDocs, DM 5.x, Docs Open 4.x
Intapp Time™: Technical Requirements
Page 9
l
Worldox GX2/3: For the capture integration to be able to integrate with Worldox, the following items must be
configured in Worldox:
n
The Worldox API must be configured such that it can be called from IIS for Time Capture in order to
use the Worldox API.
n
A search template must be configured for the Time Capture account in Worldox so that API searches
will return results across all libraries.
n
The Worldox API has limitations on the length variable in the API used to store the file path. This limitation is 80 characters for GX2 and 250 characters for GX3. Any document file paths that are too
long for the API to handle will not be able to be cross processed.
Billing System Integration
Our Time Management clients use the billing system to retrieve client, matter, timekeeper and user-defined field
(UDF) information. It has been tested to support the following billing systems:
l
Aderant Expert/CMS.NET
l
Elite 3E
l
Elite Enterprise 3.x (Microsoft SQL Server database)
l
Rippe & Kingston. Integration with Rippe & Kingston requires access to a SQL Server with a linked server
connection setup using the Microsoft DB2 OLE driver for Time Capture to access the Rippe & Kingston database.
Phone System Integration
Time Capture has been tested to support retrieving phone data from the following systems:
l
Avaya (requires configuring a second IP feed to send call data from the Avaya system to a Time Capture service)
l
Cisco Call Manger 9, 8, 7, 6, 5, 4
l
Copitrak Phone 0.2.17
l
Equitrac
l
nQueue Billback
Time Capture can also be configured to retrieve data from text files or SQL databases if certain criteria are met.
Digital Dictation Integration
Time Capture has been tested to support the following digital dictation systems:
l
Big Hand/nFlow
l
Winscribe
l
Crescendo
Server Configuration Considerations
For optimal performance, Intapp recommends hosting the Time Management Solution and its databases as follows:
IIS/Web Servers
One dedicated IIS server for the following functional roles
Page 10
Intapp Time™: Technical Requirements
l
Desktop time entry server
l
Time entry administration interface
l
Mobile time entry sever (see “Optional:” configuration details below)
Second dedicated IIS server for the following functional roles
l
Capture server
l
Capture administrative interface
Optional: third dedicated IIS server when choosing a DMZ configuration for mobile devices
l
Mobile time entry sever
Intapp Time™: Technical Requirements
Page 11
T IME E NTRY 2012/2013/2014: M INIMUM
R ECOMMENDED R EQUIREMENTS
Intapp Integration Platform
l
Intapp Integration Platform: Intapp Time requires an Intapp Integration Platform to be installed where it can
make network connections to all necessary source systems, including the Timevault database and all activity
source systems. Due to the load of the integrations, Intapp Time should be placed on its own dedicated Intapp
Integration Platform separate from other Integration Builder or Wall Builder processes.
l
Virtual Infrastructure: The Integration Platform is supported on the following virtualization software:
l
l
n
VMware ESXi
n
VMware ESX 3.5 + (Server or Cluster)
n
Microsoft Hyper-V 2008 R2+
Minimum System Requirements for the Virtual Image:
n
2x 2.0 Ghz CPU
n
4 GB RAM
n
55 GB disk space
Version: Intapp Integration Platform version 4.7.4 or greater is required for Intapp Time.
Administrative Reports Server Requirements
l
Microsoft SQL Server 2008 R2, 2012
l
SQL Server Reporting Services (SSRS)
l
32GB RAM
Workstation Requirements
l
Microsoft Windows XP SP3/Vista/Windows 7/Windows 8 (Desktop)/Windows 8.1
l
Internet Explorer 11, 10, 9, 8
l
.Net Framework 3.5 SP1
l
TCP/IP Networking
l
2GB RAM minimum, 4GB recommended with Windows 7 or higher
l
100 MB of disk space
l
VGA 800x600
Note: Citrix compatible. Citrix servers require 250-500 MB of memory per concurrent user.
eBillingHub Integration
Integration with eBillingHub requires that both the Intapp Time backend and client software are running a minimum
version of 2013.4.1.
Page 12
Intapp Time™: Technical Requirements
Intapp Time Mobile for iOS
l
iOS 5.0 and higher
Note: In order to use Intapp Time Mobile for iOS, you must use a registered work email account on the iOS device,
hosted by Microsoft Exchange Server.
Intapp Time Mobile for Good Technology
Intapp Time Mobile for Good Technology Edition is a client application for Intapp Time that allows the application to
be managed using a unified set of Good Dynamics policies and services that will perform a remote wipe of enterprise data, while leaving personal data intact.
Server & Client Requirements
l
iOS compatible devices (iPhone and iPad only)
l
Intapp Time Server and Admin Tool 12.3.3 or higher installed separately from Good Control and Good Proxy
Server
l
Intapp Time Mobile for Good Technology Edition license file
l
Good Control and Good Proxy Server installed separately from the Intapp Time Server and working
l
Good Control registered on the Good Dynamics network
Note: Good Dynamics does not support iOS 5.0/iPad 1.
Intapp Time Mobile for Android
l
Android OS 2.3.3 or higher
l
1GHz or faster processor
l
Network access
l
6MB of local storage access required for app binary file
l
20 MB of local storage required for app data storage
Intapp Time Mobile for Android supports most modern phones and tablets, but due to the wide variety of display resolutions and densities that are available, certain devices may not be supported. To determine if your specific device
is supported please visit the Intapp Time Mobile for Android application in the Google Play store at https://play.google.com/store/apps/details?id=com.entry.app. When you are logged into the Play Store with the username
associated with your device, the Play Store will tell you whether or not your specific device is supported.
Intapp Time Mobile for BlackBerry
l
5.0, 6.0, 7.0
Note: BlackBerry 10 is not supported.
Intapp Time™: Technical Requirements
Page 13
T IME C APTURE
Note: Windows Server 2003 and Windows XP should no longer be used for Intapp Time Capture components installation as these operating systems do not meet the requirements for .NET 4.5 installation.
Database Server
l
Microsoft SQL Server: Time Capture requires a Microsoft SQL Server on which to create a database. Supported versions include:
n
Microsoft SQL Server 2014
n
Microsoft SQL Server 2012
n
Microsoft SQL Server 2008 R2
n
Microsoft SQL Server 2005, SP4 and later
l
SQL Server Edition: Standard or Enterprise
l
Collation type: The database must use collation type SQL_Latin1_General_CP1_CI_AS or SQL_Latin1_General_
CI_AS.
l
Security: Time Capture requires a user name and password (either SQL or Windows) that has privileges to connect
and create a new database, tables, and other objects.
l
Minimum System Recommendations:
l
n
4x 2.0 GHz CPU with 1MB cache, or equivalent
n
6 GB RAM
n
150 GB disk space per 1000 users
n
Windows Server 2008 or 2003
Load Requirements: For a 1000-attorney law firm, Intapp recommends a SQL Server that can handle the following:
n
Database size of 8-10 million rows when in full production
n
Transaction load of 150,000 to 250,000 events per weekday in full production
Presentation Web Server (IIS)
l
Microsoft IIS Server: The Time Capture web application must be installed on a Microsoft Windows Server computer running Internet Information Services (IIS). Supported versions include:
n
Windows Server 2012/R2 (IIS version 8/8.5), 64-bit
n
Windows Server 2008 (IIS version 7, 7.5)/2008 R2, 32-bit or 64-bit
n
Windows Server 2003 (IIS version 6)/2003 R2, 32-bit or 64-bit
l
.NET Framework 4.5: The IIS server must have .NET Framework 4.5 or later installed.
l
ASP.NET 4.0: Once the .NET Framework has been installed, ensure that this version of the framework is the
one being used by IIS. This is done by selecting the web server's properties in the IIS administration console,
selecting the ASP.NET tab, and choosing ASP.NET version 4.0 from the dropdown.
l
(Windows 2003) Enable IIS Web Service Extensions: If the IIS server is Windows 2003, there may be additional steps required to enable ASP.NET pages to run. See the following articles from Microsoft support:
http://support.microsoft.com/kb/315122 and http://support.microsoft.com/kb/332124.
Page 14
Intapp Time™: Technical Requirements
l
Time Capture database connectivity: The IIS server must be able to connect to the database server hosting
the Time Capture database.
l
Unicode Font support: Time Capture supports Unicode (multi-byte character sets). For the journal reports to display Unicode properly, the font Arial Unicode MS (ARIALUNI.TTF) must be installed on the IIS server. For users
to be able to view Unicode in reports and the web application, this font must also be installed on the user’s
desktop PC.
l
Minimum System Recommendations:
l
n
4x 2.0 GHz CPU with 1MB cache, or equivalent
n
6 GB RAM
n
30 GB disk space
Latency: Users accessing the Time Capture Web Server should have latency under 200ms.
Mobile Web Server (IIS)
Note: Intapp Time Mobile is the recommended solution for clients going forward. The Mobile Web App should only be
used for firms leveraging BB10 devices or existing Time Capture Mobile Web App customers.
l
Mobility: If the firm is using the Mobility module we require an additional IIS server be setup such that mobile
devices can connect to the application hosted on the server.
l
Technical Requirements: The Mobility Web Server has the same requirements as the Presentation Web Server
(IIS) above.
l
Mobile Device connectivity: The Mobile Devices connecting to the server must be able to connect to the server
using VPN supported by the device OS or openly using SSL. As such the network configuration should be setup
such that a mobile device can reach the server using one of these two methods.
l
Mobile Hardware and Software Requirements:
l
n
iPad 1, 2, 3, and 4: iOS 5.x and 6.x
n
iPhone 3GS, 4, 4S, and 5: iOS 5.x and 6.x
n
BlackBerry: OS 6, 7, and 10 full screen devices
n
Android: OS 4.x devices
Internal Server connectivity: In addition to a connection to the Time Capture database, the Mobile server will
need to authenticate Windows credentials. If the server is placed in a DMZ, then either a firewall exception or
trust relationship may need to be set up to the appropriate server.
Intapp Integration Platform
l
Intapp Integration Platform: Time Capture requires an Intapp Integration Platform to be installed where it can
make network connections to all necessary source systems, including the Timevault database and all activity
source systems. Due to the load of the integrations, Time Capture should be placed on its own dedicated Intapp
Integration Platform separate from other Integration Builder or Wall Builder processes.
l
Virtual Infrastructure: The Integration Platform is supported on the following virtualization software:
l
n
VMware ESXi
n
VMware ESX 3.5 + (Server or Cluster)
n
Microsoft Hyper-V 2008 R2+
Minimum System Requirements for the Virtual Image:
Intapp Time™: Technical Requirements
Page 15
l
n
2x 2.0 Ghz CPU
n
4 GB RAM
n
55 GB disk space
Version: Intapp Integration Platform version 4.7.4 or greater is required for Time Capture.
Time Capture Desktop Extension (DE)
l
Windows: The Time Capture Desktop Extension (DE) client software must be installed on a Microsoft Windows
XP, Vista, Windows 7, Windows 8 or Windows 8.1 computer. DE supports both 32-bit and 64-bit operating systems.
l
Web Server Connectivity: DE must be able to connect to the Time Capture web application.
l
.NET Framework 2.0: The Windows computer must have .Net Framework 2.0 installed.
Note: If you install the .NET Framework 3.5 SP1, the .NET Framework 3.5 SP1 download page has additional requirements to address known compatibility issues with .NET Framework 3.5 SP1. If you have installed .NET SP1, please
be sure that you have also installed the appropriate KB updates as referenced on the. NET Framework 3.5 SP1 download page.
l
Desktop Applications:
n
Default applications: DE contains built-in logic to obtain detailed usage information for the following
applications:
n
Microsoft Word 2013 (32-bit & 64-bit), 2010 (32-bit & 64-bit), 2007 (SP1 or above), 2003 (SP2 or
above)
n
Microsoft Outlook 2013 (32-bit only), 2010 (32-bit), 2007 (SP1 or above) or 2003 (SP2 or above)
Note: Outlook 2013 64-bit and Outlook 2010 64-bit are not supported at this time.
n
Microsoft Excel 2013 (32-bit & 64-bit), 2010 (32-bit & 64-bit), 2007 (SP1 or above) or 2003 (SP2 or
above)
n
Internet Explorer: Time Capture officially supports Internet Explorer 8 through 11
n
Adobe Acrobat Standard/Professional X, 9, 8, or 7
n
Adobe Reader X, 9 or 8
Note: DE has been tested only with the specific versions of the applications listed above. Using DE with older versions of the applications listed above is not supported.
l
Custom Applications: DE can be configured to track usage of other Win32 applications. This is accomplished
by monitoring a specific process name. For custom applications, DE can also use the application’s window
title to track usage by the information contained in the window title.
For example:
Page 16
n
DE can be configured to track Microsoft PowerPoint by enabling monitoring of POWERPNT.EXE. Since
PowerPoint displays the document name in the window title, DE can track usage of each individual document being worked on in PowerPoint.
n
DE can be configured to monitor usage of Microsoft SQL Server Management Studio by enabling monitoring of ssms.exe. The window title tracking functionality of DE does not provide any additional
information since the window title only contains Microsoft SQL Server Management Studio regardless
of what action is being performed within the application. In this case, since no additional usage context
is available in the window title, DE will only be able to track the total time spent in SQL Server Management Studio.
n
DE can be configured to track Yahoo Messenger by enabling monitoring of YahooMessenger.exe.
Since Yahoo Messenger displays the name of the person you are chatting with in the Window title, DE
can track usage of each individual person an IM conversation is occurring with.
Intapp Time™: Technical Requirements
l
Memory Usage: DE memory use will vary depending on the number of applications enabled to be tracked as
well as the number of simultaneous items being tracked. DE will use approximately 15-75MB of RAM on average. When DE is used in a Citrix or Terminal Server environment, you should expect DE to use 15-75MB of RAM
for each remote user. A portion of the RAM used by DE (typically 15-25MB) can be, and is often, shared by other
processes.
l
Citrix: DE can track application usage when DE is installed in a Citrix server environment that is configured to
use published desktops or published applications. To use DE in a published desktop environment, you simply
install DE on the Citrix server. A separate instance of DE will run for each remote desktop user. No other configuration is needed for published desktops. To use DE for published applications, additional configuration is
required as outlined in the Time Capture Implementation Guide document. DE is not currently able to track
applications that are configured as streamed applications.
l
Virtual Desktops DE can track most applications running in virtual desktop environments the same as if they
were running on a physical desktop by simply installing DE as part of the virtual desktop image.
Time Capture Timers
l
Windows: The Time Capture Timers client software must be installed on a Microsoft Windows XP SP3 or later,
Vista, Windows 7, Windows 8 or Windows 8.1 computer. Timers support both 32-bit and 64-bit operating systems.
l
Web Server Connectivity: Timers must be able to connect to the Time Capture web application.
l
.NET Framework 4.0: The Windows computer must have .Net Framework 4.0 installed.
l
Time Capture Desktop Extension: For full functionality, Time Capture Timers requires the same version of DE
to be installed on the workstation.
Time Capture BlackBerry Extension
l
l
BlackBerry Enterprise Server (BES): The Time Capture BlackBerry Extension (BBE) is a BlackBerry Mobile Data
System (MDS) application and requires BES version 4.1.x/5.0.x, or BES Express 5.0.x.
n
MDS must be enabled on the BES.
n
The BES server must be able to connect to the Time Capture IIS Web Server.
BlackBerry devices: A BlackBerry application is installed on each BlackBerry device. This application is normally
installed by pushing out the software to the devices automatically using the BES.
n
Connection and Collaboration Services and MDS must be enabled for any device that will be using the
BBE.
n
The device must have OS 4.x, 5.0, 6.0 or 7.0.0.261+. The new BlackBerry OS 10 is not supported at this
time.
n
Device memory use: The BBE software that is installed on the device is approximately 70kb. The total
device memory used by BBE is approximately 500kb under normal usage.
Time Capture Carrier Capture
This feature requires that the carrier make the calls available through their website after the call is completed and
before the end of the billing cycle.
l
Supported Carriers
n
l
AT&T Enterprise (US)
Carriers where calls are not available through website
Intapp Time™: Technical Requirements
Page 17
n
Rogers Enterprise (Canada)
n
Bell Enterprise (Canada)
If your carrier does not appear above, our Product Management team would be happy to meet with your carrier administrator to see if we can access the calls for your carrier.
Microsoft Exchange Integration
Time Capture uses the Exchange server to retrieve contact and calendar appointments, for the QuickNote feature,
and iPhone/iPad/Android sent email activity capture. Time Capture has been tested to support the following versions:
n
Microsoft Exchange Server 2013
n
Microsoft Exchange Server 2010
n
Microsoft Exchange Server 2007
n
Microsoft Exchange Server 2003*
*Certain features of Time Capture require Exchange Web Services which is not supported in Exchange 2003. The
Time Capture QuickNote feature and capturing iPhone/iPad/Android sent email activity is not possible with
Exchange 2003.
DMS Integration
Time Capture has been tested to support using the DMS database to retrieve the client/matter assigned to a particular document for the following document management systems:
l
Autonomy WorkSite 9.x, 8.x
l
Microsoft SharePoint 2010/2007
l
NetDocuments
l
Open Text/Hummingbird DM 5.x, Docs Open 4.x
l
Worldox GX2, GX3
n
The Worldox API must be configured such that it can be called from IIS for Time Capture to be able to use
the Worldox API.
n
A search template must be configured for the Time Capture account in Worldox so that API searches will
return results across all libraries.
n
The Worldox API has limitations on the length variable in the API used to store the file path. Any document file paths that are longer than the API can handle will not be able to be processed by Time
Capture. In Worldox GX2, this limit is 80 characters. In Worldox GX3, this limit has been increased to
255 characters if the Worldox databases are using LSYS 9. Note: Please contact Worldox support for additional information or for assistance in configuring these items within
Worldox.
Billing System Integration
Time Capture uses the billing system to retrieve client, matter, timekeeper and user-defined field (UDF) information.
Time Capture has been tested to support the following billing systems:
l
Aderant Expert/CMS.NET
l
Elite 3E
l
Elite Enterprise 3.x (Microsoft SQL Server database)
Page 18
Intapp Time™: Technical Requirements
l
Rippe & Kingston. Integration with Rippe & Kingston requires access to a SQL Server with a linked server connection setup using the Microsoft DB2 OLE driver for Time Capture to access the Rippe & Kingston database.
Time Entry System Integration
Time Capture has been tested to support the following time entry systems:
l
Aderant Expert/CMS.NET
l
Intapp Time, DTE 2007, DTE 2004
l
Elite 3E
l
Elite WebView 5.3, 5.4
l
Ripper & Kingston. Integration with Rippe & Kingston requires access to a SQL Server with a linked server connection setup using the Microsoft DB2 OLE driver for Time Capture to access the Rippe & Kingston database.
l
Tikit Carpe Diem Classic 2010/Carpe Diem 4.x
l
Tikit Carpe Diem Enterprise/TimeKM 5.x, 6.x. Integration with Carpe Diem Enterprise/TimeKM requires a
license and installation of the Carpe Diem Enterprise/TimeKM SOA module.
Phone System Integration
Time Capture has been tested to support retrieving phone data from the following systems:
l
Avaya (requires configuring a second IP feed to send call data from the Avaya system to a Time Capture service)
l
Cisco Call Manger 8, 7, 6, 5, 4
l
Copitrak Phone 0.2.17
l
Equitrac
l
nQueue Billback
Time Capture can also be configured to retrieve data from text files or SQL databases if certain criteria are met.
Digital Dictation Integration
Time Capture has been tested to support the following digital dictation systems:
l
Big Hand/nFlow
l
Winscribe
l
Crescendo
Peak Load Estimates
Peak loads for the Time Capture application are estimated per 1000 users. Assumptions:
l
Average user – 75 activities per day dispersed across an 8 hour day
l
Total for 1000 users – 75,000 activities per day dispersed across an 8 hour day
l
Average activity load per second – 2.6 (75,000 activities / 8 hours / 3600 seconds in an hour)
l
Peak activity load per second – 6.0 (estimate based on average activity load)
l
Peak number of active Time Capture user browser sessions – 400
Intapp Time™: Technical Requirements
Page 19
Peak Load Tests
Intapp has performed tests of the Time Capture application under the above peak load conditions, and verified that
the application and database can load a maximum of 40.0 activities per second. Further, the application was tested
with 800 simultaneous active user browser sessions. In both test cases, qualitative manual tests were performed
confirming that the application remained responsive and showed no noticeable deterioration in performance under
these load conditions.
Server Configuration Considerations
For optimal performance, Intapp recommends hosting the Time Capture web application and the Time Capture database on separate Windows servers. These servers should be co-located and connected via a reliable Gigabit Ethernet connection.
The Time Capture web application or database server can be used in a virtual (VM) environment or as an addition to
an existing server that is shared with other applications as long as the server has sufficient available resources and
bandwidth to accommodate the additional load from Time Capture as outlined above. Before determining your production Time Capture server configuration, please discuss the various server configuration options with your Time
Capture project manager.
Page 20
Intapp Time™: Technical Requirements