Avaya For connecting to the Avaya AES server, the PegaCALL CTI Link Engine requires the Avaya AES Java Telephony API (JTAPI) SDK, release 6.3. Contact your Avaya representative to obtain the SDK. Once you have installed the SDK, locate the following files: ï§ ecsjtapia.jar ï§ log4j-1.2.12.jar ï§ log4j.propertie
Copy the files located in the step above to the Pega 7 node where you wish to install the PegaCALL CTI Link Engine. PegaCS 7.1.4 Installation Guide 22 Install the third-party Java libraries on your Pega 7 node 1. From the Designer Studio menu, select Application > Distribution > Import. 2. Choose the Java archives (.jar files) that you copied and import them into the Customer codeset (which is the default); one at a time, following Pega 7 prompts. Note: Import Java archives on only one Pega 7 node in a cluster. Once a Java archive is imported, it is stored in the Pega 7 database and is accessible to every node in the Pega 7 cluster. 3. Disable Background Class Saving with JBoss e-Tier If you have deployed Pega 7 in JBoss’ e-Tier, you must disable background class saving in Pega 7 as follows. CTI events may trigger compilation (first-use-assembly) of Pega 7 rules. Background class saving in JBoss’ e-Tier can cause compilation errors and subsequent problems with PegaCALL event processing. a. Edit the prconfig setting compiler/saveClassesInBackground and set it to false. This is typically in your prconfig.xml file. b. Restart your application server.
in fact, the jars are imported into the pega database, which means it applies to all the servers pointing to the same database (after restart). So it does not matter which server you login to import jars.
where to install SDK is not important, the import part is to be able to get those three jars mentioned in the doc after SDK installation. Pega server is simply a java client to Avaya so only jars are needed.