Plants-By-WebSphere Topology


Now that we've had a fair tour of WebSphere topologies, let's consider our sample application, Plants-By-WebSphere. As usual, when it comes to matching a configuration with business requirements, it all depends! There are a couple things we can easily conclude, however. Since Plants-By-WebSphere is an Internet storefront type application, it is designed to be accessible through the Internet by as many people as possible. So we will need a DMZ to protect our data assets. We'll place an HTTP server in the DMZ and forward all web requests to the presentation logic of Plants-By-WebSphere, running in a WebSphere application server behind the DMZ. We would most likely run a clustered server for availability: if one server or machine goes down, we still have the other one to keep our business running while we recover the failure. In addition, a cluster gives us an easy way to add more processing power to our production environment: we can expend the cluster by adding additional servers on existing or new nodes. The following diagram depicts the topology we would use to support Plants-By-WebSphere in a production environment:

click to expand

The few factors and considerations we have listed here certainly do not represent to totality of issues that you must face when designing and deploying a production topology – for example, we have not discussed security policy, which we will look at in the next chapter. However, we hope our brief consideration of the configuration characteristics appropriate to support our sample application offers added insight into the subject of topology.




Professional IBM WebSphere 5. 0 Applicationa Server
Professional IBM WebSphere 5. 0 Applicationa Server
ISBN: N/A
EAN: N/A
Year: 2001
Pages: 135

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net