# Mac OS X Installation Guide for AIQ (GraalVM 11 Based)
A step-by-step guide for installing and configuring Appvance IQ on Mac OS X.
# Download AIQ for macOS
1. Download AIQ.
If you do not have an Appvance IQ download link, please reach out to your Appvance contact, or email .
1. Extract Appvance IQ to the desired install location.
For example: `/Users//AIQ`
Next step: [Install Java GraalVM11](https://docs.appvance.net/Content/AIQ/AIQ_Install/MacOSX/Install_Mac_InstallJava.htm)
---
Last updated: July 31, 2024
If you have any feedback on this topic, please contact us at
# Install Java GraalVM 11 for AIQ
## Recommended guidance
Install Java or GraalVM 11 only when the AIQ release being deployed explicitly requires it. Current environments should always be checked against the active AIQ system requirements before changing runtimes.
## Before installation
- Confirm AIQ version, operating system, CPU architecture, and supported runtime build.
- Download from an approved source and verify the package when possible.
- Plan installation path, environment variables, service account access, and rollback.
- Back up existing runtime configuration before replacing it.
## Validation workflow
1. Confirm the runtime version from the account that starts AIQ.
2. Restart AIQ services after approved configuration changes.
3. Review startup logs for path, permission, or runtime errors.
4. Run Scenario Editor and Service Suite smoke tests before returning the environment to users.
*Last updated: October 7, 2026*
# Configure Java for AIQ
## Recommended guidance
Configure Java only according to the AIQ version and deployment model in use. Java requirements can differ across AIQ releases, operating systems, installers, and legacy integrations.
## Before configuration
- Confirm the AIQ version and the supported Java or GraalVM runtime.
- Check operating system, installation path, service account, and environment variables.
- Remove or isolate conflicting Java installations when they affect AIQ startup.
- Validate permissions for AIQ services, scripts, and Test Nodes.
## Validation workflow
1. Confirm the runtime version from the same account that starts AIQ.
2. Restart AIQ services after approved configuration changes.
3. Review startup logs for runtime, path, or permission errors.
4. Run a Scenario Editor and Service Suite smoke test after Java changes.
*Last updated: October 7, 2026*
# macOS Required Configurations for AIQ
## Recommended guidance
Apply macOS configuration steps according to the AIQ version, macOS version, CPU architecture, browser requirements, and customer security policy. Do not bypass macOS security prompts through documentation; the user or administrator should approve required permissions.
## Configuration areas
- Runtime dependencies, browser dependencies, certificates, and local permissions.
- Download quarantine, Gatekeeper, and application execution approvals handled by the user.
- Network, proxy, DNS, and firewall access to AIQ and applications under test.
- File permissions for installation, logs, repositories, and Test Node assets.
## Validation workflow
1. Confirm AIQ starts and users can log in.
2. Run Scenario Editor and Service Suite smoke tests.
3. Verify browser launch, downloads, certificates, and required permissions.
4. Document macOS version and any administrator-approved policy changes.
*Last updated: October 7, 2026*
# MySQL Install and Setup for AIQ
## Recommended guidance
Install and configure MySQL for AIQ only according to the supported database version and deployment model. Database configuration affects login, execution history, reports, upgrades, and data integrity.
## Before setup
- Confirm AIQ-supported MySQL version, host, port, storage, charset, and collation.
- Plan database user permissions, backup, restore, monitoring, and maintenance windows.
- Review firewall, network, DNS, certificate, and OS service settings.
- Document configuration values that AIQ requires during install or upgrade.
## Validation workflow
1. Confirm the database service starts after reboot.
2. Validate AIQ can connect using the configured account.
3. Run login, Scenario Editor, Service Suite, and reporting smoke tests.
4. Review database and AIQ logs for permission, packet size, or case-sensitivity issues.
*Last updated: October 7, 2026*
# Install the AIQ Database Schema
## Recommended guidance
Install the AIQ database schema only with the installer or migration process supported by the target AIQ version. Schema changes affect platform stability, upgrades, reporting, and execution history.
## Before installation
- Confirm AIQ version, database version, host, schema name, user permissions, and backup status.
- Verify charset, collation, packet size, case-sensitivity, and storage requirements.
- Coordinate downtime and rollback if the schema is being created or migrated in a shared environment.
- Use approved scripts only; do not manually edit schema objects without support guidance.
## Validation workflow
1. Run schema creation or migration from the approved installer or script.
2. Confirm AIQ can connect with the configured database user.
3. Run login, Scenario Editor, Service Suite, and reporting smoke tests.
4. Review AIQ and database logs for permission, migration, or object errors.
*Last updated: October 7, 2026*
# Update MySQL Packet Size and Case Settings for AIQ
## Recommended guidance
Update MySQL packet size and case-sensitivity settings only when required by the AIQ version, database workload, or support guidance. These settings can affect imports, upgrades, reports, and cross-platform database behavior.
## Before changing settings
- Back up the database and current MySQL configuration.
- Confirm the exact variable names, target values, and MySQL version.
- Coordinate downtime if a database restart is required.
- Document why the setting is being changed and who approved it.
## Validation workflow
1. Apply changes in the correct MySQL configuration file or managed service setting.
2. Restart MySQL if required and confirm the active values.
3. Run AIQ login, scenario, service, report, and upgrade-related smoke tests.
4. Review logs for packet, table-name, permission, or migration errors.
*Last updated: October 7, 2026*