IBM WebSphere

Selecting application server is part of architechtural process when infrastructure is defined. It depends on several facots:

1. External systems your application will be interacting

2. Type of application you have

3. Target availability of system.

4. Corporate standards

5. Budget.

If you use JDBC type (I) driver you dont need to add any driver in websphere. you simply created DSN and use it locally, same we use java class, if you use Type(2) and Type(4) so first go to admin console then go to connection, then add driver there fill other info like conn. size, uname pass, max conn. and connect it to you applications.

ApplicationServer: takes care of Security, Transaction, Multithreading, Resource pooling, load balancing, clustering, performence, highly availability, scalability, etc. Exposes business logic to client applications through various protocols, possibly including HTTP. Supports deployment of .war and .ear filesApplication server = webserver + EJB container.

Webserver: handles HTTP protocol. Receives HTTP request, it responds with an HTTP response.

1. open WSAD

2. go to project

3. click properties

4. select javaBuildPath

5. add any jar file like jaxp select add external jars.

1. Directly copy files to deployedapplication folder in websphere- hot deployment.

2. use websphere specific ant tasks and building automated scripts for deploying application.

3. through administration console.

There are 2 ways to install WAS.

1. Install through GUI

2. Silent Installation.

Webpshere tends to focus more on integration, connectivity and web services. it has rich implementation of J2EE, better performance, more extensive integration and transaction management. In terms of trnsaction weblogic is having default transaction attribute as ’supports’, but websphere does not have any default transaction attribute.

Webpshere tends to focus more on integration, connectivity and web services. it has rich implementation of J2EE, better performance, more extensive integration and transaction management. In terms of trnsaction weblogic is having default transaction attribute as ’supports’, but websphere does not have any default transaction attribute.

Websphere is from IBM and Weblogic is from BEA.

Change the WebSphere server's server variables using the Administrative Console or use scripts.

WAR or EAR files.

Can be installed using Administration Console or scripts.

Deployment descriptor is an XML file that describes how to deploy a module or application by specifying configuration and container options. For example, an EJB deployment descriptor passes information to an EJB container about how to manage and control an enterprise bean. There are two types of deployment descriptor in websphere: Web application deployment descriptor and portlet deployemnt descriptor

Portlets are packaged as WAR files with a web application deployment descriptor (web.xml). This defines each portlet as a servlet within the web application, including unique identifiers for each portlet, the portlet class, and initialization parameters.

JBoss Is an Application Server that supports J2EE

IBM Websphere and BEA WebLogic servers are a combination of Application Server, Web Server & container

Jakarta Tomcat is a Servlet container and a Web server.

Apache Sever is a Web server

IBM provides several industrial strength development environments based on Eclipse development framework the current IDE is Rational Developer for Websphere. Applications can also be developed with the Websphere Application Server Toolkit and third party tools like Jbuilder, and Eclipse/ANT etc.