Defining IP Ranges for 8.4 deployment by NodeType
Hello everyone,
First time working on Pega Deployments. We are deploying Pega 8.4 Platform in AWS Private Cloud. We are deploying on Amazon Linux with Tomcat and PostgreSQL. Given architecture, we want do deploy by node classification (Batch, Stream and WebUser). Each nod type will be associated with an Application Load Balancer, all instances will be under same VPC and may be in 2 subnets. i have couple questions.
- To communicate between Nodes, i may need to provide Batch Node IP address to Stream and WebUser
- Since nodes are behind Load Balancers, how can i provision IP range in Stream and WebUser instead of individual IP address, which may change down the line
- What is the best way to build search indexes in this scenarios.
Thank you in advance
Great-West Financial
US
Does anyone have answer or let me know, if i am not thinking in right direction. Any guidance is appreciated on this.
Pegasystems Inc.
US
You should ensure all nodes (including database) are in the same subnet for performance's sake. As long as all these nodes can communicate to each other, the rest should be transparent to Pega, no manual ip configuration needed normally. Search indexes will be built automatically to the index directly (-Dindex.directory can be used to specify the location on a persistent disk). However, index building is in the background so you should be able to login long before that is done which can take some time. Use Admin Studio to check the progress through queue processor screen or search landing page on the dev portal. Hope this helps!