Question
Cognizant Technology Solutions
CA
Last activity: 14 Mar 2018 17:23 EDT
Minimizing number of CTI connections generated by Pega
Hi,
In Production we have 24 nodes and in each node CTI link engine is running which creates 24 different connection at Cisco CTI Server end.
1. Is there any way we can reduce the number of connection without disabling CTI link in any node?
2. Is it possible that more than one node can use only one connection?
Thanks
***Updated by moderator: Lochan to add Categories***
JPMorgan Chase & Company
US
Cognizant Technology Solutions
CA
We are using Cisco ICM/UCCE and the article you mentioned describes basic CTI Link setup.
My question was -
Suppose I have 24 Nodes in Production and in each node we have Local CTI Link configured as a result of which at Cisco side we are seeing 24 connection established. Is there any way we can make multiple Pega Node to use single connection pool with while interacting with Cisco so that number of connection would get reduced?
Can we use Remote CTI Link for the same ? In case of remote CTI are we going to have one connection pool or multiple between the server where Local CTI Link is configured and Cisco?
What are the pros and cons of having Remote CTI link over Local CTI link?
Thanks
Pegasystems Inc.
IN
Hi Purushotam,
Yes. Using Remote Link configuration should reduce the connections at the Cisco side.
But for that you should expose the local link CTI as SOAP services and then use the link in the remote CTI link configuration.
Thanks,
Hanisha
Pegasystems Inc.
US
- Why do you want to reduce the connections to cisco?
- What are you trying to accomplish?
- Are all the users on the 24 nodes CTI enabled users?
Depending on the answers to the above questions I will be able to provide you better feedback.
A little additional info: Do keep in mind he remote setup that will introduce more moving parts. You will now have SOAP calls involved along with CTILink engine connections. With the remote setup you will need dedicated JVMs configured that will run only ctilink engine and nothing else. If you were to reduce from 24 nodes / ctilink engine down to 6 then you will need to make sure those 6 can handle the load and are sized properly since you have now taken the load across 24 ctilink engines and concentrated it to 6. Also you will probably need to look at sizing the requestor pool for the soap calls as well. Failover options change once in introduce the remote setup and it does make things a little more complicated from both operational and debugging.