Everything that applies to creating a reasonable, maintainable WebSphere Application Server environment on distributed platforms (AIX, Linux, Windows, whatever) also applies to the mainframe. You should have a cluster, preferably with the cluster members on different LPARs on different boxes. If that's not possible, then have the cluster members on different LPARs on the same box. If that's not possible, I recommend that you have a cluster (of perhaps just 2 nodes) on a single LPAR. Why? Even though it adds a few extra address spaces, I think the benefits of maintainability are significant. With a cluster, you can apply maintenance, either to Java, WebSphere, or your application, to one of the nodes, and leave the other node up, handling requests. No down time. You don't get that benefit if you are running with a single controller with multiple servants.
The document which you referenced is for WebSphere XD, and it's not clear that you need to go down that path (although it definitely has some cool functionality). One place to go is to the IBM Techdocs site (http://www.ibm.com/support/techdocs/atsmastr.nsf/Web/Techdocs - watch for wrap), and search for "WebSphere and z/OS", and any documents by Bagwell or Hutchinson are usually going to be very valuable. Load balancing - Sysplex Distributor provides good load balancing on the front end, plus if they are webapp requests, using the WebSphere plug-in in the HTTP server works great. If you are balancing EJB requests, if you are running a cluster it's pretty much built in to the ORB. You may have to do a little tuning to get it perfect. Should you have the WebSphere Application server on the same LPAR as DB2? Probably. If you do, then you can use jdbc type 2 connections, which provide better performance than type 4. However, if you have zIIP(s), I don't know if you would get a better ROI by using the type 4 driver. I was told at least a year ago that there was going to be a paper coming out comparing the two, but I have yet to see it. Aaron On Wed, 12 Dec 2007 00:05:28 +0330, legolas wood <[EMAIL PROTECTED]> wrote: >Hi, >Again it's me, with my newbie like questions. >I have no experience with mainframes so I always think to map mainframe >world with intel based servers world. >If we have an J2EE based application which we need to deploy on >WebSphere application server, and our J2EE application uses DB2 as its >database, what can be possible deployment schema if our system need to >be highly available, assume that we have redundant network >infrastructures, power supply and a secondary site in another >geographical location. > >What I am looking to understand is how our application server instances >and DB2 instances will run inside the each mainframe. > >I find some information from the articles available in IBM web site, >articles like : >https://www6.software.ibm.com/developerworks/education/webspher e/0708_faulhaber/index.html > >I found that ODR will act as load balancer instead of web server that I >used with dell servers. >But I can not understand do we install all ODR instances and real work >load servers into one single operating system? >Or we should install several instance of zOS into mainframe LPARs and >then install each of these instances into a separate operating system ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
