Hi,

We are facing an issue with the WEBLM License verification.

From the application logs, we could notice that for the first call after tomcat service start, the WEBLM license verification is returned as true, but for the following calls the license verification is returned as false and it is going into the Grace time period.

Below are the Environment Specification

AEP Version: 7.1.0
Tomcat Version: 8.0.15
OD Version: 7.1
WEBLM license Version: 7.x

We have tried the following steps but the issue still persists and is not resolved.

1. Enabling TLS on the Tomcat server.xml and configuring the 8443 port for a HTTPS connection and mapping the HTTPS url in the AEP application.

2. Adding the WEBLM and SMGR root certificates to the trusted_weblm_certs.jks file

3. Adding the trustedcert.properties and the trusted_weblm_certs.jks file to the /webapps/xxxxx/WEB-INF/lib/ folder.


Please find attached the screenshots of the Application log for reference.

Can you take a look at the report.log in the data/log directory or on EPM reporting? There maybe an error logged somewhere. We need to find out what the error is when trying to retrieve the licenses.

Hi Wilson,

Please find attached screenshot of the error received in AEP report.


Error obtained is :

Runtime License Error :com.avaya.weblm.LicenseException: Problem with connection to server: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

3. Adding the trustedcert.properties and the trusted_weblm_certs.jks file to the /webapps/xxxxx/WEB-INF/lib/ folder.

Your 3rd step. The files should be in the Tomcat_Home/lib directory same place as the weblm.jar not the app directory.

Hi Wilson,

The trusted_weblm_certs.jks and trustedcerts.properties were never moved from the tomcat/lib folder.

Initially the files were present in that folder only and the issue was observed

As per the suggestion in another devconnect post related to the same issue, the files were copied and placed in the webapps/xxx/web-inf/lib folder.

The files were always present under the tomcat/lib folder.

We never recommended having the files in webapps/xxx/web-inf/lib. That might cause conflict. I can only guess at this point since I've never seen such problem before only with the files in Tomcat/lib.

Hi Wilson,

Could you suggest any other steps that we could try for resolving this issue.

We tried adding the weblm url certificate to the cacerts of the jre installed in the system.

Could this help?. Have you faced similar problems elsewhere?

Have you removed the files from the webapps/xxxx/WEB-INF/lib directory?

Also I am not sure why you did step 2:

2. Adding the WEBLM and SMGR root certificates to the trusted_weblm_certs.jks file

It's not in our standard procedure. I am not certain if that has something to do with the problem. Again I have not see such problem that it works once and stops working.

Hi Wilson,

Is there any specific setting that needs to be enabled/disabled while generating the war file from the OD application?

Are there any specific methods of war file generation in relation to the WEBLM license verification.


Also, Can you kindly mention the standard procedure that needs to be followed?


Thanks,
Akash

The application deployment or the war file does not have anything to do with the WEBLM files. The WEBLM files are packaged in common runtime zip file. As the first step in the standard deployment procedure for preparing the app server, you use the Export Runtime Support Files wizard to generate the runtimesupport zip file, and expand this into the app server home directory. The zip file should contain the WEBLM files you need for every application you deploy afterwards.