cancel
Showing results for 
Search instead for 
Did you mean: 

XI 3.1 Deployment Scenarios

Former Member
0 Kudos

We currently have XIR2 SP2 using a SQL 2005 database, with the applications on one server and the database on another sever, two servers. In the XI 3.0 Deployment Planning Guide some of the scenarios for the server tier have a Framework server, which I believe should include the Input, Output, Event, and CMS servers. With the upgrade to XI 3.1 is it necessary or good practice to have a separate Framework server or have all servers (services) on one as we currently have with XIR2 SP2? What are the advantages of having a Framework server?

Also is it good practice to have a separate Web-App server running Tomcat? Would this help performance issues with XI 3.1?

Any response would greatly appreciated.

Mike

Accepted Solutions (1)

Accepted Solutions (1)

BasicTek
Advisor
Advisor
0 Kudos

Well XI products were designed to scale, so if you need more then you can simply distribute your environement across servers.

I'd say #1 get you DB alone (you did that on your existing system)

#2 get your web/app on a seperate server, then if needed seperate your services (framework server)

#3 finally add extra servers(clustering)

There is an XIR2 performance guide in the articles section. It all depends on how much processing is needed. XI 3.x performance guides are still pending I believe.

Regards,

Tim

Former Member
0 Kudos

Tim,

Thanks so much for your reply.

Our system usage will be 10 concurrent licenses and 10 named licenses. Based on this, I'm still not sure if we would be okay to install all applications on one server or split. If we did split servers, would it be better to run Tomcat on the Framework server or the server (machine) with all other servers (services) or have a separate web-app server (machine) as you mentioned.

Thanks,

Mike

BasicTek
Advisor
Advisor
0 Kudos

Unless you want to hire a consultant to examine your particular setup, requirements, and propose a solution the next best thing may be the [sizing guide|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e01588cd-c73e-2b10-018c-fe083bc6e05e] I mentioned earlier

You can always start with an all in one server and add distributed parts when you run into bottlenecks.

Regards,

Tim

Answers (0)