- Edrawings 2015 x64 minimum requirements pdf#
- Edrawings 2015 x64 minimum requirements software#
- Edrawings 2015 x64 minimum requirements windows#
Once an index is built, the server is also used to run the conceptual features such as categorization and clustering. The analytics server is responsible for building and storing the conceptual indexes in the environment. For example, Relativity uses the service bus for submitting conversion jobs to agents and returning converted documents.įor more information, see Relativity Service Bus documentation. This infrastructure feature supports this communication by routing messages between application components. The Relativity service bus is a message delivery service that communicates information about agent jobs to different application components. All confidential information is stored securely in the Secret Store database that can be accessed only from authenticated servers.įor more information, see Relativity Secret Store. A secret could be user credentials, a database connect string, an instance setting that contains confidential information such as your SMTP credentials, or a TLS certificate. The Secret Store is a required component that provides secure, auditable storage for Relativity secrets. Note: Refer to the Processing page for a breakdown of performance metrics. Therefore, it is suggested that 8 logical cores and 16GB RAM be allocated to each worker server to get the most throughput. Each processor core and 2GB RAM will create two threads. Relativity has placed a hard cap on the amount of threads that each Worker server is allowed to spawn, the hard cap is 16 threads. The ‘Worker’ role is responsible for handling enhanced native imaging and processing jobs.
![edrawings 2015 x64 minimum requirements edrawings 2015 x64 minimum requirements](https://i.ytimg.com/vi/8L8lZik_buU/maxresdefault.jpg)
Edrawings 2015 x64 minimum requirements pdf#
This server is also used for native imaging and save as PDF request management. Total memory and processor requirements for this role are not as demanding as the SQL Servers that house workspace databases. Processing has individual store databases that correspond to each Relativity workspace database with processing enabled. SQL Server (Invariant/Worker Manager server) In addition to workspace databases there are Relativity system databases present on each server that contain tables for system configurations, agent job queues, users/groups, etc. Environments may have one or more SQL Servers. Each Relativity workspace is represented by its own SQL Server database. This SQL Server is where the structured text and metadata resides for the documents. Therefore, each Relativity agent server that is designated to be a dtSearch search agent server should only have one dtSearch search agent and nothing else. One dtSearch search agent may be able to utilize all available processor cores on a server. Conversion jobs are multi-threaded and one conversion agent may utilize all available processor cores on a server.įor more information, see Required configurations for new deployments.ĭtSearch queries are multi-threaded and spawn as many threads as there are sub-indexes or cores - whichever number is lowest will be the constraint. 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.
Edrawings 2015 x64 minimum requirements windows#
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.
![edrawings 2015 x64 minimum requirements edrawings 2015 x64 minimum requirements](http://pfmabe.software/wp-content/uploads/2015/04/cygwin_install_error.png)
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.
Edrawings 2015 x64 minimum requirements software#
These system requirements contain detailed information about the software and hardware you use to host Relativity in your environment and in the cloud.