PegaCall CTI integration with Avaya AES ecsjtapi.jar version
Hi,
We want to reinstall ecsjtapi.jar in our application by removing the older version of the jar from the server. To do this we have already deleted the jar from pr_engineclasses table and also from the temp directory in tomcat. After restarting the server we see that on the Version Information landing page of Pega Call Administration & Configuration it still shows the old version is accessible. Can we proceed to import the new version of the jar file and if it is imported will it override the old version ?
Thanks
Yasser
***Edited by Moderator: Lochan to update platform capability tags***
Accepted Solution
Cognizant Technology Solutions
GB
Solution -
The correct process to update any external jar file is to import the new api in a new Customer codeset version.
Update the DSS "properties/com.pega.pegarules.bootstrap.codeset.version.Customer/default" with the new codeset version.
Pegasystems Inc.
IN
Hi Danish,
Thanks for posting the query. Could you please check whether the updated jar version is present in the prengineclases table?
Cognizant Technology Solutions
GB
We have checked prengine_classes table and it contains the latest version of the jar file. Before importing the new version we made sure that the previous version was deleted. We have have found that after restart Pega is loading the old jar file to ..prweb/extractedFiles/apploader directory and hence we are not able to use the new version. Before restarting the app server we made sure that all copies of the old jar was deleted from this directory or any other.
Accepted Solution
Cognizant Technology Solutions
GB
Solution -
The correct process to update any external jar file is to import the new api in a new Customer codeset version.
Update the DSS "properties/com.pega.pegarules.bootstrap.codeset.version.Customer/default" with the new codeset version.
