SimpliLoad is a lightweight, Docker-based utility that enables IBM Cognos Analytics users to run reports through the REST API using a clean, modern interface. This guide explains how to deploy SimpliLoad using the Azure Marketplace offering, including VM provisioning, configuration, access, and connectivity to Cognos Analytics.
SimpliLoad requires IBM Cognos Analytics 12.1.3 or later. Earlier versions are not supported because required REST API endpoints are unavailable.
Open the Azure Marketplace listing for SimpliLoad, select your desired plan (Trial, Single, or Unlimited), and click Create to launch the Azure deployment wizard.
Configure the foundational Azure resource settings for your virtual machine:
rg-simpliload-prod) to keep all deployment assets grouped logically.simpliloadvm).ssh-rsa) for secure Linux authentication. If you need to generate a new key pair, open PowerShell and run: ssh-keygen -t rsa -b 4096 -f "$env:USERPROFILE\.ssh\id_rsa" (the public key will be saved to $env:USERPROFILE\.ssh\id_rsa.pub).Select the hardware tier appropriate for your workload capacity:
Standard_D2s_v4 (2 vCPUs, 8 GiB RAM).Standard_D2s_v4, Standard_D4s_v4, or Standard_D8s_v4 based on concurrent report volume.Configure initial application credentials and network access parameters:
SimpliLoad secures all web traffic using HTTPS. You must choose how application and CA certificates are provisioned during deployment:
If your enterprise uses internally signed or enterprise CA certificates, upload the corresponding PEM-encoded files:
SimpliLoad automatically mounts these credentials into /opt/simpliload/deploy/certs/ for the NGINX reverse proxy container to ensure secure, trusted connections.
If you leave the certificate upload fields blank, SimpliLoad automatically generates a secure self-signed certificate upon first boot. While fully encrypted, your browser will display an initial security warning until you trust the certificate locally or replace it later. If a public IP address is configured, it is automatically injected as a Subject Alternative Name (SAN).
Configure networking settings for your deployment:
New to create a dynamic or static public IP, or select None to keep the virtual machine entirely private within your network.<prefix>.<region>.cloudapp.azure.com.Azure runs a final automated validation check against your parameter inputs. Once validation passes, click Create to provision the infrastructure and trigger the automated installation script.
SimpliLoad enforces an allowed-hosts list for security. During deployment, the VM's hostname and any provisioned public IP address are automatically added to ALLOWED_HOSTS.
To reach the SimpliLoad interface, inbound traffic on Port 443 (HTTPS) or Port 80 (HTTP) must be permitted:
https://simpliload-prod.eastus.cloudapp.azure.com/
simpliload-vnet to route traffic over Azure’s private backbone.Regardless of whether SimpliLoad is deployed with a Public or Private IP, it acts as a load generator that must initiate outbound connections to your Cognos Analytics environment.
Ensure your Network Security Groups (NSGs) and corporate firewalls allow outbound traffic from the SimpliLoad VM to your Cognos server:
Direct SSH access is completely optional and disabled by default. If your team requires SSH access, you must first open Port 22 via an inbound Network Security Group (NSG) rule or connect through an Azure Bastion / private VPN.
Once network access is established, authenticate using the RSA key created during deployment:
ssh <admin-user>@<hostname-or-private-ip>
Note: If you generated your key using the default path ($env:USERPROFILE\.ssh\id_rsa), your SSH client will use it automatically without requiring additional flags.
Docker containers are located under:
/opt/simpliload/
All Cognos configuration is performed inside the SimpliLoad UI.
On the Settings page, enter:
Click Test to verify connectivity.
To update SimpliLoad:
docker compose pull
docker compose up -d
This section provides practical guidance for diagnosing and resolving common issues encountered during deployment or operation in Azure. Each item includes likely causes, recommended fixes, and steps for reviewing logs inside the SimpliLoad VM.
Common Causes:
.env is incorrect.Fixes:
.env points to the correct file..env configuration if self-signed defaults trigger a mismatch.Common Causes:
COGNOS_ALLOW_HTTP=false in .env while Cognos is only serving HTTP.Fixes:
curl -v https://your-cognos-host or curl -v http://your-cognos-host.COGNOS_ALLOW_HTTP=true in .env and restart the stack.Common Causes:
Fixes:
Important: If an API key is locked, expired, or deleted in Cognos Analytics, it cannot be recovered. A new key must be generated and updated in the SimpliLoad Settings page.
Common Causes:
Fixes:
.env on the VM and increase ASGI_THREADS, then run docker compose up -d to apply changes.SIMPLILOAD_RUN_TIMEOUT_SECONDS in .env for complex reports and restart the stack.Common Causes:
Fixes:
.env have not been modified after deployment.The SimpliLoad VM stores all configuration files, certificates, and Docker resources under a single directory. These files are useful when troubleshooting, enabling DEBUG logging, or verifying certificate installation.
/opt/simpliload//opt/simpliload/.env/opt/simpliload/deploy/certs//opt/simpliload/docker-compose.ymldocker compose logs -f simpliload-web-1
docker compose logs -f simpliload-nginx-1
docker compose logs -f simpliload-db-1
Logs are streamed from containers rather than stored as files.
These locations are consistent across all Azure plans and do not change when resizing the VM or updating SimpliLoad.
Recommended Diagnostic Workflow:
docker compose logs -f simpliload-web-1 to identify application-level errors.docker compose logs -f simpliload-nginx-1 for certificate or routing issues.docker compose logs -f simpliload-db-1 for database initialization or storage issues.LOG_LEVEL=DEBUG in .env for deeper insight into Cognos REST interactions, then run docker compose up -d to apply changes.Note: Always returnLOG_LEVELtoINFOafter troubleshooting to avoid excessive log output.