It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×7,469
×5,940
×4,318
×2,351
×1,436
×1,298

question asked: Apr 20, 1:53 p.m.
question was seen: 674 times
last updated: Apr 24, 7:09 a.m.

Related questions

ELM 703 DOORS minimum production topology and server specs

0
Sean F (1.3k●2●52●162) | asked Apr 20, 1:53 p.m.

Is it possible to run the reporting applications on the same server as the core applications if the production deployment is for a small 5 user setup running on Windows servers?

If so what would the minimum approximate machine specs be?

If the reporting apps must be on a separate server then is it just DCC and LQE that should be on the reporting server or should RS also be on the reporting server?

2 nodes would give 3 servers altogether:

Application
JTS+RM+CCM+GC+LDX+RS

Reporting
DCC+LQE

Database
DB2

What would be typical approximate ballpark minimum specs (cores + RAM) for these 3 machines for a small 5 user deployment with an initially small database?

Specs can be increased later as virtual server resources are dynamically configurable.

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Davyd Norris (2.8k●2●17) | answered Apr 21, 7:58 p.m.
Hi Sean,

It's more about the volume of data than the number of users but I have everything installed on a single virtual machine with 12G RAM and 2 x 2 cores assigned and it runs really well.That's the DB2 server as well as the ELM full set of apps.

If you were dunning DB2 on a separate server then I reckon you could run with 8G for the apps and 8G for DB2
Comments
Ralph Schoon commented Apr 24, 3:15 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Davyd,

this is OK for a demonstrator, but it is likely not going to provide the best experience in the long term, depending on the usage of course.
0
permanent link
Sean F (1.3k●2●52●162) | answered Apr 23, 1:00 p.m.
edited Apr 23, 1:03 p.m.

Thanks Davyd.

I also have had evaluation environments running with all apps + DB2 on one server with 16GB ram and 8 logical cores with no problems.

Based on this practical experience I was anticipating that a production deployment would simply involve upgrading the machine specs to something beefier and putting DB2 on its own DBS machine.

But when I ran the interactive deployment guide for 703 it flagged up that a separate server is needed for reporting apps (the 702 interactive guides did not flag this)

The 703 interactive deployment guide then links to the topology page on the wiki. This page lists departmental topology as the minimum production topology

https://jazz.net/wiki/bin/view/Deployment/StandardTopologiesOverview#Departmental_topologies

This topology page says that even for evaluation environments you need a separate server machine for reporting. It says for production deployments the minimum topology is 3 ELM nodes with DCC and LQE each requiring their own separate server machines apart from JTS+RM+CCM etc. (plus DB2 database server making a 4th machine).

Seems like overkill based on my experience but it must have been documented that way by somebody at IBM for some reason.

Comments
Ralph Schoon commented Apr 24, 3:14 a.m. | edited Apr 24, 3:16 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

It might sound surprising, but we have a team looking at the deployment architecture, refining the guidance in the deployment wiki. Different applications have different requirements with respect to disk space, disk I/O, RAM, CPU, etc. and this is also changing. It is not always obvious, why the recommendations are the way they are, but they reflect our current understanding and best practices.

Ralph Schoon commented Apr 24, 7:09 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

I do not think that we have any sizing for 5 users. 

If you start with one server, it would be possible to replace that server with a reverse proxy and to move the applications to new servers to scale up. This way you can keep the public URI (e.g. https://myserver.example.com/ ) on the proxy and forward the requests to the servers hosting the applications without having to do a server rename.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.