Run the ServiceNow application installer -Manual install Self-hosted

[jeffreyluto]

In this article https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0563844#mcetoc_1irbns9a83i

When doing an install on a 2 node system with 4 -8 JVMs for Servicenow on each directory do I have other options for this install call line?

$ java -jar glide-<release version>.zip -m dist-upgrade -c sample_16000 -a

For example if an already backing up service with incremental and full backup and at the point of the upgrade doing VMsnapshots is there a flag or option the skips the local file backup process ( it wastes time)?

Also is there way to pass into the installer command java every dir on the host? like see below

java -jar glide-<release version>.zip -m dist-upgrade -c sample_16000 sample_16001 sample_16002 sample_16004 sample_16003 -a

Or do I have call each one individually? And can I call JVM on another host in the list in the same command line?

Is there a flag that skips checking if the service is off and stopping the service? I do I hard rolling stop of the services before upgrading; that check for the service being off seems to waste time also.

Any ways that I can call and run script faster?

Also see attached is it ok to run the script like this? Basically I am calling the installer in succession in a bash script?

[jnte3355]

I am looking for a way to perform the dist-upgrade but leave the node stopped.  This would be helpful because:

• When having nodes started as a systemd service, this manual start means that systemd does not recognize the node as running. This will confuse systemd operations on the node (systemctl status will  show the node as Inactive, systemctl stop will not actually stop the node).
• Performing an additional node restart after dist-upgrade is not always straightforward since there might be user sessions and jobs started on that node.

Of course other solutions for this problem are welcome too!

[jnte3355]

I just noticed that you can pass --help argument like this:

java -jar <glide zip file> dist-upgrade --help

However I think this doesn't directly answers to your needs @jeffreyluto but I am interested to understand what this option actually does, could this be what I am asking for above?:

-o|--upgrade-war-only [optional for mode: dist-upgrade: default: off]

[jeffreyluto]

It spits out this:

--help

[-m|--mode] MODE [modes: install, dist-upgrade]

-d|--dist-file DIST_FILE [optional for mode: install, dist-upgrade: default: executing zip/jar]

-s|--dst-dir DST_DIR [optional for mode: install: default: $(INSTANCE_NAME)_$(PORT)]
-n|--instance-name INSTANCE_NAME [required for mode: install]
-p|--port PORT [required for mode: install]
-x|--extra-properties EXTRA_PROPERTIES [optional for mode: install: comma separated list of key value pair (eg: x=1,y=2,z=3)]

-c|--current-dir CURRENT_DIR [required for mode: dist-upgrade]
-t|--test-mode [optional for mode: dist-upgrade: default: off]
-o|--upgrade-war-only [optional for mode: dist-upgrade: default: off]

Examples:

1) Install a new node into directory test_16001:

java -jar glide-washingtondc-12-20-2023__patch10-hotfix3b-05-20-2025_05-23-2025_1940.zip install -n test -p 16001

2) Install a new node into directory test_16001 with an extra property:

java -jar glide-washingtondc-12-20-2023__patch10-hotfix3b-05-20-2025_05-23-2025_1940.zip install -n test -p 16001 -x glide.installation.developer=true

3) Upgrade an existing node in directory test_16001 (a WAR or dist based directory):

java -jar glide-washingtondc-12-20-2023__patch10-hotfix3b-05-20-2025_05-23-2025_1940.zip dist-upgrade -c test_16001

Useful properties:

glide.cluster.node_name=test-node-name
glide.servlet.prefix=/custom-context-root
glide.proxy.host=https://test.service-now.com
glide.proxy.path=/

[jeffreyluto]

--dist-file DIST_FILE  ( might be what I need or an trying to accomplish with the bash script that calls the installer a few times?)

--upgrade-war-only   ( would this be if you want to just upgrade the files but not the database on the instance?)

-x glide.installation.developer=true (for servicenow install used for Development instance? what does that really mean?)