System Requirements
Component Name | Description | Requirements |
---|---|---|
SQL Server |
|
|
Analytics Processing Server[2] |
|
|
AI Server (optional) |
|
|
Web Server |
|
|
Caching Server[4](optional) |
|
|
File Server (optional) |
|
|
3rd party integration |
|
|
Client side |
|
|
Note
[1] Depending on implementation and project load, these servers may be stacked into one box configurations.
[2] For one language, estimate 500k to 1M documents analyzed and written to database per day, per analysis processing server box.
[3] AI Server may need 4 GB memory per 1 million documents during active COSMIC analysis. If using High Precision Classification (HPC), recommend increasing Memory to 64 or 128 GB.
[4] By default caching server uses port 6379, make sure other servers can access this port on caching server.
User Accounts Requirements
Account Name | Description | Permissions |
---|---|---|
NexLP Service Account |
|
|
The NexLP Service Account is used to set up IIS application pool on the Web Server. If the attribute “manualGroupMembership” for processModel is set to “true”, this user will need to be added to the IIS_USERS group, see the link below for more details:
https://docs.microsoft.com/en-us/previous-versions/iis/settings-schema/ms689446(v=vs.90)
Also notice the NexLP Service Account needs to have “Log On As A Service” privilege. This can be done through Local Security Policy, refer to the link below for more details:
The common language runtime (CLR) integration feature is off by default. Check MSDN to enable it for the output SQL server, refer to the MSDN article here: