Posted: 5 May 2017 3:45 EDT Last activity: 12 May 2017 5:11 EDT
Pega Co-Browse and Pega Chat setup
We want to setup a POC environment with Pega Chat and Pega co-browse. As per the installation guide below are the software requirements
Linux-Based Operating System based on kernel version 3.16.0-31-generic or Red Hat Enterprise Linux version 3.10.0-327.36.3 el7.x86_64
I have few queries regarding this setup
1. The hardware specification mentioned for each one of the software as mentioned in the installation guide is mandatory? Can we run this with les hardware than mentioned?
2. As mentioned in the "Recommended Setup" section of Co-Browse installation guide "Each individual Node.js, Redis, and Mongo server should be deployed on separate Linux machines". Is it mandatory? Or only recommended? Can run all of this in same server?
3. Can we setup both Pega Chat and Pega Co-Browse in same server?
4. As both Pega Chat and Pega Co-Browse needs same software requirement, so can't we use same setup for both? Or need separate setup in separate machine?
I have attached the installation docs. Please help.
The recommendations are for a live production setup. Here are responses to your queries:
Yes, you can run on a less powered hardware. Infact if this is for a small POC just to get your hands dirty, you can run on your desktop as well. As long as the version specs are met of course.
For a dev/demo setup you can install Node, Redis, Mongo on the same system.
Co-browse and Chat can be setup can be installed on the same server. But you have to make sure that they are running on separate ports and accessing separate databases. Also, the redis cannot be shared between Co-browse and Chat.
As mentioned above, the redis must be separate. You don't need a different machine, as long as you can figure out that 2 redis instances can run on the same machine and on different ports. You can have just one MongoDB, but you will need to create 2 separate databases for Co-browse and Chat. And finally the 2 products will have to run on their own ports and obviously separate Node js runtimes (which can again be on the same machine).