Home / Installation / Server Tier
The PxStat Application Server Tier Installation and set up.Please read the Requirements first.
Create ainetpub/pxstat/ws/server
folder where to copy the compiled code of the Server tier.
FYI, ws
stands for Web-Service.
ws
folder created above. Run the following code to create the public
and private
Hard Links / Directory Junctions.
mklink /j private server
.
mklink /j public server
.
Hard Links. A hard link is the file system representation of a file by which more than one path references a single file in the same volume. N.B. You will need to be logged into the Command Prompt as an Administrator.
Compile the C# code according to the relevant environment (TD, UAT, Live) and publish into theserver
folder.
Open the Server Certificates at the root level of the IIS Server.
Import the SSL Certificate for your domain.
N.B. Take note of the Application pool
name (i.e. PxStat WS
). You will need this name later when setting the permission for the Performance Monitor Users.
private
and public
folders to Applications.
Open the Advanced Settings
of the application pool PxStat WS
and change the Maximum Worker Processes
to 0
.
Implement this at the pxstat\ws
level only.
To access IIS click on your Start menu and double click on Server Manager
.
Add Roles and features
.
Click on Next to continue.
Click on Next to continue.
Select Windows Authentication
within the security options.
.
Install, close and open IIS.Select Internet Information Servies (IIS) Manager
from the Tools
menu on the Server Manager dashboard.
Required
and select the Enable Kernel-mode authentication.
Set NTLM
as the only Enabled Provider.
Open the Configuration Editor
at the root level of your IIS Server.
Please note these settings can be tuned according to your environment and requirements.
system.web/httpRuntime
section.maxRequestLength
to cap any request size. maxRequestLength
is expressed in KB (Kilo Bytes). If you want to upload up to 10 MB files, then you must allow some extra Bytes (i.e. 1 MB) required by the JSON-RPC request, for a total of 11 MB = 11 * 1024 = 11264 KB.executionTimeout
to limit the execution time of any request.N.B. The maxRequestLength
and executionTimeout
at the Server level must be equal or greater than the maxRequestLength
and executionTimeout
set in the Web.config
of the application:
<system.web> <compilation debug="true" targetFramework="4.7.2" /> <!-- executionTimeout (Seconds), maxRequestLength (KB) --> <httpRuntime executionTimeout="3600" maxRequestLength="11264" targetFramework="4.7.2"/> </system.web>
system.webServer/security/requestFiltering
section.requestLimits/maxAllowedContentLength
to cap any request size. maxAllowedContentLength
is expressed in B (Bytes). If you want to upload up to 10 MB files, then you must allow some extra Bytes (i.e. 1 MB) required by the JSON-RPC request, for a total of 11 MB = 11 * 1024 * 1024 = 11534336 Bytes.N.B. The maxAllowedContentLength
at the Server level must be equal or greater than the maxAllowedContentLength
set in the Web.config
of the application:
<security> <requestFiltering> <!-- maxAllowedContentLength (B) --> <requestLimits maxAllowedContentLength="11534336" /> </requestFiltering> </security>Add the
Application pool
name (i.e. PxStat WS
) to the Performance Monitor Users group.
IIS APPPOOL\PxStat WS
and click on Check Names to validate.iisreset
for all changes to take immediately effect.RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4