The path to the architect 15th day installation and optimization of IBM WebSphere (i)

First, Ibmwebsphere

When he began to touch ejb1.x in 02, there was a huge, plump book called "EJB from Getting Started to mastering (master ejb2.0)", the red-skinned, Wrox company published. The book comes with 1 CDs, with 3 app servers in the CD.

1. Jboss2.2.1

2. Weblogic6.1

3. IBM Websphere applicationserver5.x

From then on began to know, Oh, the original 3 big manufacturers are to do Java-ee containers. Sure enough, today these three containers are still in the world's undisputed status.

So, we talked about Tomcat+apache (cluster), Weblogic+apache (cluster), and the basic application and concept of WebSphere are not going to escape.

Websphere now occupies a major position in any IBM product, with virtually all IBM enterprise-class applications such as IBM ILog Jrulz, IBM Lombardi, IBM Websphere Portal Server, IBM TAM, etc. , the first of these products is to install IBM Websphere Application Server or IBM Websphereapplication Server network Deployment (WASND) first on your server.

It is therefore essential that we learn and master the installation of IBM was, integration with IBM Httpserver (IBM's improved commercial Apache Server), and wasnd (used as the IBM was installed version of the cluster).

Ii. Basic Concepts

IBM's family of products uses the JDK of IBM itself, and this JDK has been improved by IBM, known as IBMJDK.

The JDK is not quite the same as our traditional JDK, Oracle-sun, and not trying to apply the tuning parameters of the previous series of Oracle Sun's JDK to the IBM jdk, which is completely wrong.

Furthermore, the integration between the IBM JDK and IBM Websphere application Server (was) is strictly required:

IBM WAS6. X can support JDK1.5, if your project is useful to JDK1.6 characteristics, then do not want to run on the ibmwas6.x.

The IBM was7.x version can support JDK1.6, but you should not think that running on ibmwas6.x can run as far as IBM was7.x, because some projects use the features of the IBM JDK, for example, some projects used IBM JDK in the WebService, the result in the 6.x run very well, to the 7.x on the dead or alive, there is no way, this is the IBM JDK, it is a big company, so modified some things for its own interests to serve. Unlike our Oracle Sun JDK, which is currently in accordance with the standard, the high version must be compatible with the low version of what is compiled.

This problem is because it has happened before, with the project team using SSH2 (struts2+spring3+hibernate3), the result of the customer's environment is IBM WAS6. X, while project development with tomcat6.x and jdk1.6, results in the actual production environment of the failure, although later through a series of tools such as patches can be WAS6 in IBM. X on the project to work, but the front has brought a very bad impact on customers.

To this end, IBM also has a set of development tools bound to its was: IBM rad,ibmrad7.0 only support was6.x, and IBMRAD7.5 that later version can support to WAS7.0 and support the related characteristics of JDK1.6, so if your engineering environment is all IBM's was related environment (was very expensive, the three products are the most expensive to be this is, can afford this customer is not a bank or a large insurance company), then also please you better use IBM RAD to develop related projects, so that customers pay the money is!