If you downloaded the software as a compressed (ZIP/RAR) folder:
Once logged in, the "Getting Started" wizard typically appears:
Before beginning, verify the following:
You may be wondering: Should I upgrade from ISM V5 or perform a clean ISM v6 software install?
| Scenario | Recommendation | | :--- | :--- | | Existing V5 with complex rules | In-place upgrade supported (backup first!). Use the Upgrade wizard option. | | Existing V5 with performance issues | Fresh install V6 on new hardware, then migrate data via import/export. | | No prior installation | Fresh install (this guide). | | Demo or lab | Fresh install with embedded SQL Express. | ism v6 software install
Warning: An in-place upgrade from V5 to V6 is irreversible. The database schema changes permanently.
sudo ./ism-v6-linux-x64.bin --mode console If you downloaded the software as a compressed
oc create secret docker-registry ibm-entitlement-key \
--docker-server=cp.icr.io \
--docker-username=cp \
--docker-password=<your-entitlement-key> \
--docker-email=user@example.com
Even experienced admins encounter issues. Here are the top five failures during ISM v6 software install and how to fix them.
| Error Message | Likely Cause | Solution |
| :--- | :--- | :--- |
| "Failed to create database" | Service account lacks dbcreator rights. | Grant dbcreator server role to the account, or temporarily use sa account. |
| "Port 8080 is already in use" | Another web app (e.g., Tomcat) is listening. | Change ISM port to 8090 or stop competing service. |
| "IIS Metabase is not compatible" | Missing ASP.NET 4.8 in IIS. | Run %windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i |
| "MSMQ queue creation failure" | MSMQ installed without HTTP support. | Uninstall MSMQ and reinstall with the MSMQ-HTTP feature. |
| "Timeout during schema migration" | Slow disk I/O or low SQL memory. | Increase SQL Server memory limit and run DBCC CHECKDB before retrying. | Before beginning, verify the following: You may be
oc get pods -n isvg-system
oc get svc -n isvg-system
Wait for all pods to reach Running or Completed state (10–15 minutes).