Any Relativity agent server designated as a conversion agent server should only have one conversion agent deployed. In Relativity 9.6 and above, viewer conversion jobs are handled by the Conversion agents. The agents can be scaled vertically and horizontally to accommodate organizational needs. The agents run under a Windows Service and often require various levels of CPU, RAM and I/O, depending on the job type. When a user submits a job, such as a Production or OCR job, the associated agent(s) will pick up the job and complete the work. User sessions can be load balanced with the included Relativity User Load Balancer or via available hardware load balancing solutions.Īgents in Relativity are responsible for running all background processing tasks. There are different mechanisms for authentication into the system including forms, active directory, two-factor, SAML 2.0, and OpenID Connect. It authenticates the user with the system, contains APIs for searching and third-party applications, transfers documents to the end user in the Relativity Viewer, and is responsible for communications during imports and exports in workspaces. The Web Server is the gateway for all users to access Relativity. As illustrated in the following diagram, all areas of the platform are scalable providing support for any hardware vendor, hypervisor, and storage protocol. NET framework with a Microsoft SQL Server back-end.
Relativity is designed with a scalable infrastructure that you can tailor to the requirements of your environment. Required configurations for new deployments.This page contains the following sections: These requirements also provide various recommendations for configuring a new deployment of Relativity, as well as scaling your environment as the number of users and the amount of data continue to grow. These system requirements contain detailed information about the software and hardware you use to host Relativity in your environment and in the cloud.
0 kommentar(er)
