Sapience Server Hardware Requirements

The recommended frequency for syncing data from Sapience Agent to the server, chosen based on data sensitivity and resource availability.

A type of synchronization that occurs every 30 minutes, ideal for keeping data consistently updated with minimal impact on resources.

A synchronization frequency set between 4 and 5 hours, suitable for scenarios where frequent updates are not critical.

A synchronization method designed to update metadata, such as user information or data structures, once a day.

A synchronization method that updates data related to meetings and information from Outlook Web, with a recommended cycle of every 8 hours.

The recommended storage capacity for a year's worth of data collected by Sapience, assuming archival policies are in place.

The minimum hardware configuration recommended for running a Sapience server, capable of handling the processing and storage demands of data analysis.

A dedicated server designed specifically for handling database operations related to Sapience, ensuring optimal performance and stability.

Storing data at different time intervals for long-term retention.

Data is kept daily for a year, then moved to long-term storage.

Data is kept weekly for two years, then moved to long-term storage.

Data is kept monthly for three years, then moved to long-term storage.

A server system with separate hardware for running applications and managing databases.

The number of users that a software system can handle simultaneously.

Balancing the workload between multiple servers to improve performance and availability.

A dedicated server responsible for running applications like Sapience Live.

The Application Server and Database Server should be connected using high-speed Ethernet (at least 1 Gbps), and they should be in a single physical data center.

A copy of the production environment used for testing and development, ensuring consistency between the two.

A weekly backup of the production database, stored on a separate server for disaster recovery.

This involves testing new features, updates, and configurations before they are implemented in the production environment.

A dedicated server that mirrors the production environment for testing purposes, ensuring consistent data.

A backup policy that includes taking a temporary backup of the Sapience databases to a separate physical location to prevent data loss.

The application server that runs Sapience Live, requiring Windows Server 2012 or later, .NET Framework 4.7.2 or higher, IIS 7.0 and above, and Microsoft Access Database 2016 (64-bit).

Microsoft SQL Server 2012 or later, designed to manage the data collected by Sapience.

A server setup with separate hardware for running applications and managing databases, with the application server and database server working together seamlessly.

Opening up specific ports on the Sapience server and client devices to allow communication between the Sapience application server, database server, and client devices. Common examples include HTTPs ports for secure web browsing and TCP ports for other server interactions.

A domain account with system administrator privileges, necessary for managing both the application and database servers, including tasks like installation, upgrades, and accessing database folders.

A standard domain account with sufficient permissions to communicate between the IIS (Internet Information Services) and SQL database server.

The ability to connect to the Sapience web client and server, both internally and externally, through protocols like HTTPS and VPN depending on security policies, allowing users to access Sapience from various locations.

A strong password policy that mandates a minimum length, specific character types (numbers, uppercase, lowercase, special characters), and regular password changes.

A group of users with specific permissions on a system. In this case, IIS_WPG and IIS_IUSRS have access to manage web applications and interact with the system.

A security policy that restricts the ability of an account to log in locally to a device. It enhances system security.

Allows accounts to submit batch jobs, such as scheduled tasks, on a server.

Grants accounts the right to run services that run in the background of a system. It's crucial for server functionality.

Prevents accounts from accessing a computer remotely through remote desktop services.

The ability to read, insert, update, delete, and execute data within the database.

The software platform necessary for running Sapience Buddy on Windows computers.

Software components required to support the C++ runtime library for running Sapience Buddy on Windows.

Open communication ports on user desktops and the Sapience Server are needed for successful connectivity. Port 443 is commonly used for secure web traffic.

The minimum version of Android required for running Sapience Buddy on mobile devices.