Clients can be a web browser, a standalone application, or other servers, and they run on a different machine from the Java EE server.

Click on the image below to view it full size in an image viewer !
Clients can be a web browser, a standalone application, or other servers, and they run on a different machine from the Java EE server.

We are now getting a huge amount of reuse of the analysis model that was setup. Let's look at how the existing model is leveraged and extended to interpret the source text sentence in UML:

We already had 2 different kinds of *Server, a general one, and a more specific JavaEE one (which provides a specific JavaEE *Serve Interface via a Port), and although they have the same unqualified name, they are from different Namespaces. Note that the Generalization from the JavaEE server to the more abstract one implies that a JavaEE server can act as a client to another JavaEE server, so-called "Generalization feedback". Note also that the JavaEE *Server also inherits the usage Port requiring the *Serve Interface !

We are now told that 'Clients .. run on a different machine from the Java EE server.', which is slightly different from (more specific and restrictive than) the previous claim: The client tier consists of application clients that access a Java EE server and that are usually located on a different machine from the server. . This is indicated with a named Dependency (and for repeating concepts a stereotype can be used). To reinforce the idea of different machines "instance-like" Properties are used to create a mini "composite structure collaboration" within the «wrapper» Component, with a Connector indicating a network. Beware however that other «wrapper» Components won't "see" this collaboration, it is local to the context provided by this «wrapper» Component.

Visit also