Install ASI

This page lists the minimum hardware and software requirements to install ASI. To run ASI, you must have a supported operating system, hardware that meets or exceeds minimum requirements, a supported database, and a supported browser.

Hardware recommendations

ASI requires the minimum system resources:

• Minimum recommended memory: 10GB
• Minimum recommended CPU: 4

For ASI installs which will see high traffic, it is recommended to increase the memory and CPU allocation.

Filesystem Recommendations

It is recommended to create separate filesystems for application and log data to improve performance, security, and manageability.

	Mount Point	Owner	Group	Permissions	Minimum Size
Application Files	/opt/ISS/logs	ppadmin	ppusers	0750	10GB
Log Files	/opt/ISS/asi	ppadmin	ppusers	0750	20GB

By separating these filesystems:

• Application Files can benefit from optimized storage without log growth impacting performance.
• Log Files can be managed independently, ensuring faster write operations and better handling of large log data.

Supported Databases

ASI requires PostgreSQL 15+ with the following extensions:

• PostgreSQL version: 15 or higher (PostgreSQL 15+)
• Required extensions:
  • semver: semver extension
  • pgcrypto: pgcrypto extension

Database User Requirements

Ensure that the database user (typically postgres) used during the installation has sufficient privileges to:

• Create databases
• Create users
• Create roles

Database Instances

The following databases will be automatically created if they do not already exist, Do NOT create these manually:

Database Name	Owner	Extensions
asidb	asiadmin	semver, pgcrypto
authdb	authdbadmin	None
vaultdb	vaultdbadmin	None

Supported web browsers

ASI supports the current version of the following browsers. Older versions of these browsers might not be supported, so you should always upgrade to the latest browser version when using ASI.

• Chrome/Chromium
• Firefox
• Edge

Software

We would recommend that your server(s) are subscribed to standard Linux repositories so that any dependant packages can be automatically downloaded prior to installation. If there are security reasons that don’t allow this on your environment, please contact support for a list of required dependant packages.

License

Contact support for a license prior to starting the application

Sudo Rules

The following sudo rules need to be added to enable the ppadmin user to manage the platform. You may also need additional sudo rules to allow your userid to be able so su to the ppadmin user.

Restart iss-asi group of services

ppadmin ALL=(root) NOPASSWD: /bin/systemctl stop iss-asi.target, /bin/systemctl start iss-asi.target, /bin/systemctl restart iss-asi.target, /bin/systemctl status iss-asi.target

Restart authenticator service

ppadmin ALL=(root) NOPASSWD: /bin/systemctl stop iss-asi-authenticator.service, /bin/systemctl start iss-asi-authenticator.service, /bin/systemctl restart iss-asi-authenticator.service, /bin/systemctl status iss-asi-authenticator.service

Restart legacy service

ppadmin ALL=(root) NOPASSWD: /bin/systemctl stop iss-asi-legacy.service, /bin/systemctl start iss-asi-legacy.service, /bin/systemctl restart iss-asi-legacy.service, /bin/systemctl status iss-asi-legacy.service

Restart management service

ppadmin ALL=(root) NOPASSWD: /bin/systemctl stop iss-asi-management-service.service, /bin/systemctl start iss-asi-management-service.service, /bin/systemctl restart iss-asi-management-service.service, /bin/systemctl status iss-asi-legacy.service

Restart core service

ppadmin ALL=(root) NOPASSWD: /bin/systemctl stop iss-asi-core.service, /bin/systemctl start iss-asi-core.service, /bin/systemctl restart iss-asi-core.service, /bin/systemctl status iss-asi-core.service

Restart dashboard service

ppadmin ALL=(root) NOPASSWD: /bin/systemctl stop iss-asi-dashboards.service, /bin/systemctl start iss-asi-dashboards.service, /bin/systemctl restart iss-asi-dashboards.service, /bin/systemctl status iss-asi-dashboards