Step 8: Sign in for the first time

Sign in as the administrator, change the default password, and set up licensing and reporting before you give users the address.

The commands on this page load their variables from openlm-install.env, the file you created from the installation worksheet.

8.1 Sign in

Open https://<your address>/ in a browser and sign in with the built-in administrator account: username admin and the default password Admin123!. OpenLM Platform asks you to set a new password immediately.

Do this immediately after step 7

The default password is the same in every installation. Until you change it, anyone who can reach your address can sign in as administrator. Sign in and change it before you give users the address.

8.2 Upload the license, then activate products

Do these two steps in this order:

1. Upload the license file that OpenLM sent you.
2. Activate the products your license covers.

License first

If you activate products before you upload the license, OpenLM Platform remembers "not licensed" for about 12 hours, even after you upload the license.

8.3 Install the reporting views

Reports and Power BI read the reporting database's views. The database gets its tables automatically, but the views come from a set of SQL scripts (001_… to 025_… for this release) that OpenLM sends with each release. If you didn't receive them, ask OpenLM support for the reporting scripts for your OpenLM Platform version. After OpenLM Platform has run for about 15 minutes, run the scripts in order:

source ./openlm-install.env
for f in $(ls 0*_openlm_sqlserver_*.sql | grep -v rollback | sort); do
  echo "== $f"
  sqlcmd -S "$SQL_HOST,$SQL_PORT" -d "${DB_PREFIX}_reporting" -U "$SQL_USER" -P "$SQL_PASSWORD" -C -i "$f"
done

In SQL Server Management Studio (SSMS) or another SQL Server client, open each script and run it against the <prefix>_reporting database, in the same order. Certain scripts print warnings, which is expected. Don't add -b to sqlcmd: it turns those warnings into failures and stops halfway.

8.4 Keep what you need for upgrades

Store these files together in a safe place:

• openlm-install.env, in your password vault, because it contains passwords
• openlm-values.yaml and gateway-values.yaml
• create-openlm-secrets.sh

An upgrade uses the same files with a newer OPENLM_VERSION. Use the same helm upgrade --install command as in step 6, including --timeout 60m. An upgrade waits 10 to 30 minutes for the topic setup job, like the installation. Plan for that in the maintenance window.

Done

Your users can now sign in at https://<your address>/.