System Requirements

Mentioned below are the minimum requirements to run AssetExplorer. You may require more RAM space and high-end processors depending upon the support load, simultaneous access load, and other applications' load installed on the same server.

* - PostgreSQL bundled is configured as a database.

If you have more than 30k scannable nodes, it is recommended to have separate remote servers for every 30k nodes to minimize the load on the central server.

Non-GUI Windows machines (or server core installation) are not supported.

Requirements for Scanning Assets

AssetExplorer uses Endpoint Central agent to scan assets. Endpoint Central is auto-installed in the same folder as AssetExplorer, by default.

If EndpointCentral is purchased separately, please refer here for detailed hardware requirements based on the number of assets purchased.

Refer to the below link for more details on the EndpointCentral agent: EndpointCentral Agent in AssetExplorer.

Additional Requirements

Supported Browsers

We recommend you update to your browsers to the latest version for better performance and security. AssetExplorer can be accessed from the following browsers:

• Mozilla Firefox
• Google Chrome
• Microsoft Edge

Recommended screen resolution: 1366 x 768 pixels.

Post upgrade to build 6977, AssetExplorer will not be accessible in Internet Explorer 11.

MSSQL

If AssetExplorer runs on MSSQL setup, ensure the database server is hosted in a separate machine under the same network as the application server. The database server configuration solely depends on number of databases configured and usage. Consult with your DBA or Microsoft MSSQL support for system requirements.

Supported MSSQL Versions: 2016, 2017, 2019, and 2022.

Enable Read Committed Snapshot Isolation (RCSI)

Enable read committed snapshot isolation (RCSI) to prevent MSSQL lock issues from affecting AssetExplorer's performance.

• Stop AssetExplorer application.
• Log in to SQL Management studio.
• Take the AssetExplorer database offline by executing:
  1. USE master
  2. GO
  3. ALTER DATABASE <db_name> SET OFFLINE WITH ROLLBACK IMMEDIATE
  4. GO
• Enable the read committed snapshot by running
  1. ALTER DATABASE <db_name> SET READ_COMMITTED_SNAPSHOT ON WITH ROLLBACK IMMEDIATE
  2. GO
• Bring the database online using
  1. USE master
  2. GO
  3. ALTER DATABASE <db_name> SET ONLINE
  4. GO
• Check if you have enabled RCSI successfully by running the following query
  1. SELECT is_read_committed_snapshot_on FROM sys.databases WHERE [name] = '<db_name>'
  2. If the query output is 1, RCSI is successfully enabled. You can start the application.

For more information on MSSQL databases and RCSI, go here.

Benefits of enabling the MSSQL Snapshot Mode

• Simultaneous user-querying of the database without any delay or disruption (although load on the application might exceed the usual limits).
• User querying records will be maintained in a separate tempdb, which will not be affected by other user queries occurring in parallel or subsequently.
• Database tables will be updated only after a transaction reaches completion.

MSSQL Database Configuration

We strongly recommend you to have an initial database capacity of at least 5GB and extend it periodically by monitoring the current database file size to avoid triggering auto-growth event unnecessarily. This will ensure optimum application performance and smooth data processing.

To configure fIle autogrowth for the database file, click here.

Creating Database:

Run the following query to create a database:

Extending Database Size:

• Find the current database size by running the query below
  1. USE master;
  2. GO
  3. select (size*8)/(1024*1024) from sys.master_files where DB_NAME(database_id)=assetexplorer and physical_name like '%.mdf%';
  4. GO
     
• Run the following query to add 5 GB to the current database size
  1. USE master;
  2. GO
  3. ALTER DATABASE assetexplorer
  4. MODIFY FILE
  5. (NAME = <dbname>,
  6. SIZE = <currentdbsize+5GB>);
  7. GO
     

Configure File Autogrowth Settings

Default autogrowth settings in the SQL Server engine may lead to disk fragmentation and performance issues. We recommend that you configure default values as fixed values instead of percentages to ensure optimum application performance.

Follow these steps to configure File Autogrowth:

• Log in to SQL Management studio and run the following query:
  1. USE <db_name>
  2. EXEC sp_helpfile
  3. GO
• If the configured growth values for Data (.mdf) and Log (.ldf) files are less than the recommended values, run the following query:
  1. USE master;
  2. GO
  3. CREATE DATABASE <db_name>
  4. MODIFY FILE ( NAME = N'', FILEGROWTH = 256MB )
  5. GO
  6. ALTER DATABASE <db_name>
  7. MODIFY FILE ( NAME = N'_log', FILEGROWTH = 128MB )
  8. GO
     
• Re-run the query in step 1 and check if the autogrowth values now correspond to the recommended values.

PostgreSQL (Applicable for versions 10.0 and earlier)

Since PostgreSQL 9.2 requires users to modify kernel resources to allot required resources for Postgres server,

• Add the the below mentioned entry in /etc/sysctl.conf
  1. kernel.shmmax=536870912
  2. kernel.shmall=131072
• Execute sudo sysctl -p /etc/sysctl.conf to reload the configured change.

This is only applicable for Linux OS installations that use bundled Postgres.

Anti-virus Scan Exemption

Any anti-virus software such as Symantec running on the same system as AssetExplorer can affect the performance of your application. If you have any anti-virus software set up in your system, we recommend you exempt AssetExplorer directories from the antivirus scan or be cautious about using anti-virus software on the same system.

If the output to this query is 1, you've successfully enabled RCSI.
You can now start the application. For more information on MSSQL databases and RSCI, go here.

Have questions regarding the System requirements to run AssetExplorer? Please let us help you. Kindly mail us your requirement by clicking assetexplorer-support@manageengine.com.