914360 wrote:Don't take it the wrong way but if you are deploying this for a client shouldnt you be the experts and not asking the question on a forum?
If we have essbase 1 and essbase 2 in same environment.
Essbase 1 will be for Essbase Only applications, where in Essbase2 will
deploy planning apps on it.Essbase 2 box will also have Planning installed.
Both essbase servers will share partitions.
Do you agree to this architecture? will it improve performance for our client?
What pros and cons you see with this model?
Edited by: 914360 on Oct 22, 2012 6:26 PM
Sorry which company do you work for?
All your previous questions looked like exam questions and you didn't take the time to even bother to mark them helpful, correct, answered.
What do we mean by same env for essbase 1 and essbae2 here ..are they on same machine/box
and if we are talking of env in sense of dev/prod/test , then yes you will have 2 essbase instance ,pointing to same HSS , an Essbase partitioned application can span multiple servers, processors, or computers.
You can have 10 Essbase servers if you want to in one environment but that has nothing to do with performance. Not sure what you're planning to put on the share but if you're thinking on putting the Essbase data files on a share you will have a negative performance outcome. If you want to split the Essbase apps from the Planning apps, what you're suggesting would make sense but you can't just say that will cause better performance specially not knowing what this "share" is.