We are using Pega PRPC 7.1.7 version and we are using iText 5.5.2 for generating pdf in our application. There is a requirement to add some hyperlinks in the pdf which is not supported by the existing iText version, we wanted to upgrade the version. The existing iText related classes are seen in the table - pr_engineclasses. As part of upgradation we downloaded the latest iText jar file and deployed it - as we do the normal Pega deployment. The new classes are not getting reflected in pr_engineclasses table, but the jar file is seen in Tomcat installed machine - C:\Pega_Temp\StaticContent\global\ServiceExport.
When we try to add the new class in the library its throwing error. Did we miss anything here?
When you say deploy, you mean import your jar using import wizard? There is a potential conflict in your approach, I would suggest you put your jar under tomcat lib directory and use SMA to check if the class is actually loaded from that location (versus from pega engine table). There are other non-standard hacks to disable pega OOTB jars, but I would like to try my suggestion first.
Pega GCS suggested me to go for the import wizard. Now I tried placing the jar file in the tomcat lib folder - C:\apache-tomcat-7.0.52\lib and restarting the server. It is not reflecting in SMA -> Advanced -> Module Verison Report and it is not found in the pr_engineclasses table as well.
Putting under tomcat lib directory will NOT insert anything to the pr_engineclasses table, that is the whole purpose here (versus import, which will insert classes into the table). You need to check SMA>>Advanced>>ETier Runtime, then do a java class up with fully qualified class name.