Kumar Amit wrote:Hi Friends,
I am planning to package webapp.war and ejbapp.jar in a single .ear file. Do I need to display both webapp.jar and ejbapp.jar in the deployment diagram in addition to .ear file OR displaying single .ear file is sufficient?
Kumar Amit wrote:Also, do I need to specify hardware profile i.e. CPU, RAM, disk configuration, network requirements of machines in deployment diagram? If yes, then how?
Does this mean that I don't need to show application components in the deployment diagram e.g. JSF/JSP and EJBs?
In chapter 9 of Mark cade's book, he has shown web and app server together in a single cluster. I am planning to show web server seperately from app server even though my web app and ejbs are deployed in a single .ear. Is this an overkill?
Also, do we need to show software profile in addition to hardware profile of the devices e.g. OS - Linux etc in the deployment diagram. Chapter 9 of Mark Cade's does not show software profile.
Sharma Ashutosh wrote:You can create process boundary or the box in the deployment diagram. Encapsulate your H/W, O/S within that box/boundary - show the upper boundary as firewall.
Thanks Ashutosh. So you mean keep all h/w and s/w of the presentation & business tier, web servers and load balancer in one box and DB cluster h/w and s/w in another box?
Kumar Amit wrote: Can you guide where to display the concrete vendor specific details (both software and hardware) e.g. type of Web server (e.g. IBM HTTP server/Apache), application server (IBM Webshere Application server / Oracle Weblogic) and database (Oracle/DB2)?
Ranganathan Kaliyur Mannar wrote:I am beginning to think about including JSPs in the class diagram - we can argue they are actually servlets and so they are classes and so can be included in the class diagram (and of course, am panicking and don't want to take risks!)...
Ranganathan Kaliyur Mannar wrote:
but, by specifying vendors, do we put ourselves at risk? for ex. what if I don't mention weblogic and oracle as vendors? will guys at Oracle not like it?