Hi Per anders Wicklund,

That's quite easy. Create an almost squared pic, rename it to login-bg-cust.jpg and copy it into the following folder:

Client Login: <ALM-Deployment>\webapps\qcbin\images

No restart or redeploy needed. Works instantly.

For the Site admin and Web login I'm not sure, because I always use the customization way via <ALM-Deployment>\application\20qcbin.war\...

Siteadmin: <ALM-Deployment>\application\20qcbin.war\webadmin\static\img\login-background.3ea36cd1.png  (ALM V24.1.P1. You have to look for yourself in the analog path in qcbin\...

Web Runner Login <ALM-Deployment>\application\20qcbin.war\webrunner\assets\images\login\login-background.png

Thank you....  yes... the first part is all per the manual (even though the manual needs some updates on pathnames), but for some reason I have only got the very simple 128 x 128 image to appear once or twice - all other times it returns the standard screen.

and still:

I located a total of four jpg files of 279 KB - including E:\QC1701P1\ALM\application\20qcbin.war\webadmin\static\img\login-bg.a5838c0b.jpg  - which contained the regular login image.

Replacing all those 4 occurrences by my new image, "webadmin" now returned the new image.

However, a regular ALM login via client launcher in 19 cases out of 20 (approximately) returns the standard image - and I can't see any 'system' in what makes it work every once in a while.

Any ideas - or time for a support ticket?
The random behaviour is definitely a 'no-go' for a client production installation.

Hi,

1. well, I can link you to OT-Knowledge Base site https://portal.microfocus.com/s/article/KM000015671?language=en_US

but I don't think that's another way, as I described. Maybe your pic is too small. My actual login screen is 2292x2475 pix.

2. I'd try to delete my content in temp folder %temp%\TD_80.

3. I have a script for daily / seasoning picture update which works instantly.

       xcopy .\login-bg-cust.jpg C:\ALM-Deployment\webapps\qcbin\images /F /Y

BTW here is the How to from the update & installation guide:

Customizing the qcbin Application

Perform the following procedure to customize the qcbin application

1. On the machine on which ALM is installed, open a file browser, and navigate to <ALM installation path>\ALM\application\20qcbin.war.

2. Open another file browser, and navigate to <ALM deployment path>\application\20qcbin.war.

3. In the installation directory, navigate to the file that you want to customize.

4. In the deployment directory, under 20qcbin.war create the same folder structure that contains the file in the installation directory.

5. Copy the file from the installation directory and paste the file in the appropriate folder in the deployment directory.

6. Edit the file in the deployment directory.

7. Run the Server Deployment Wizard from

Thank you for the suggestions...

I attempted the steps 1-7 above, but it failed to re-deploy, with a message starting with:

Unexpected exception occurred:
java.lang.UnsupportedClassVersionError: com/microsoft/sqlserver/jdbc/SQLServerDriver has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
...
....
....

which all seems odd, as the java version on the server is a very recent build:

E:\QC1701P1\ALM>java -version
openjdk version "1.8.0_402"
OpenJDK Runtime Environment (Temurin)(build 1.8.0_402-b06)
OpenJDK 64-Bit Server VM (Temurin)(build 25.402-b06, mixed mode)

You have to use JDK 11 or later. I suggest JDK 17

stackoverflow.com/.../class-has-been-compiled-by-a-more-recent-version-of-the-java-environment

Thanks Pascal....

That was an unexpected development, as Opentext has Java 8 as their recommended environment in the 17.0.1 Support matrix.

/Per Anders

Did you try it?

Not yet, as I will need to check with the client if Java 11 is permissible. Levels above 11 are not supported according to ALM 17.0.1. compatibility matrix.