Production dialog instance running on QA system

[Former Member]

Hello everyone,

We are looking adding additional dialog instances (app servers) to our R3 environment. As cost is an issue, we were considering one of the following:

1.

We have 3 R3 systems (ecc6, BI7, and SRM), and 1 Portal system (all production).

We are considering adding a DI to these systems, however, hosting it on another system (i.e. QA, Sandbox, etc).

or

2. adding one new server, and having 4 application servers system.

Is this type of architecture supported/ok to build? We would like to add some extra wp's to our production system, and give them extra ram, cpu cycles etc... however, do not think we can afford a separate server for each application server.. However we need to make sure there are no cavorts with this idea.. Can anyone let us know if either of these scenarios would work well?

Thank you

Richard

[Former Member]

Hey guys,

Thank you so much! Appriciate all the info.. this was very helpful.

[JPReyes]

I agree, i would be thinking in getting a nice sized box and split it in 3 or 4 virtual servers and accomodate the dialog instances on them... advantage is that you wont have a single point of failure from the software point of view, is cheaper and greener... you can also allocate resorces on demand if required.

Anyhow... thats my 2 cents

Regards

Juan

[ImtiazKaredia]

Technically this should not be a problem. You can host different app servers on one physical hardware with different instance numbers.

But then your application server needs to be sized correctly.

A better option will be of using VPAR or LPAR and install one app on one partition.