This topic highlights Web sites and other ideas for finding best practices for designing WebSphere applications, particularly in the realm of WebSphere extensions to the Java 2 Platform, Enterprise Edition (J2EE) specification.
When designing WebSphere applications, follow the example set by the Samples. Refer to the code in the Samples Gallery that is available with the product. In particular, the Samples Gallery highlights new and WebSphere-specific aspects of the programming model.
Consult the architectural suggestions in Application design consideration .
Use the following links to find relevant supplemental information about designing WebSphere applications. The information resides on IBM and non-IBM Internet sites, whose sponsors control the technical accuracy of the information.
These links are provided for convenience. Often, the information is not specific to the IBM WebSphere Application Server product, but is useful all or in part for understanding the product. When possible, links are provided to technical papers and Redbooks that supplement the broad coverage of the release documentation with in-depth examinations of particular product areas.
The authors, who are IBM consultants and performance experts, describe this document in the following way: Over the last five years, a lot has been written about J2EE best practices. There now are probably 10 or more books along with dozens of articles that provide insight into how J2EE applications should be written. In fact, there are so many resources, often with contradictory recommendations, navigating the maze has become an obstacle to adopting J2EE itself. To provide some simple guidance for customers entering this maze, we set out to compile the following "top 10" list of what we feel are the most important best practices for J2EE.
Patterns for e-business are a group of reusable assets that can help speed the process of developing Web-based applications. The patterns leverage the experience of IBM architects to create solutions quickly, whether for a small local business or a large multinational enterprise.
This document is older (2001), but its focus on the fundamentals of Web and Enterprise JavaBeans (EJB) application programming helps it stand the test of time.
The author states: In this article I explore the reasons why some WebSphere Application Server applications use XSL for HTML production instead of JavaServer Pages (JSP) files. I will compare the performance of XSLT for HTML/XHTML production against JSP files and browser formatting. I will then provide guidance on how to improve XSLT performance in WebSphere Application Server should you decide to go this route. While this article focuses on the use of XSLT for the production of HTML, the performance best practices are directly applicable to other WebSphere Application Server uses of XSLT, such as XML-to-XML transformations and XML-to-text transformations.
The author states: Web services performance comes of age in WebSphere Application Server Version 5.0.2, but just as with more traditional J2EE applications, the performance of Web services applications is largely determined by the design of the application and the database. This article considers the application design factors unique to Web services performance, including the most important: moving to WebSphere Application Server 5.0.2. I will examine the performance of WebSphere Application Server 5.0.2 Web services and establish some best practices for optimizing Web services performance on WebSphere Application Server 5.0.2.
This tip is a little dated in its details, but the premise remains true. It describes how to separate static content from a WebSphere application so it can be served by the Web server instead of the application server. Separating static Web content (HTML, GIF, CSS files, and so on) from dynamic Web content (servlets and JSP files) allows processing capacity to be split between the Web server and application server. You can then allocate capacity between the two based on the amount of dynamic and static content in your site. If your site serves mostly static content, it is more cost effective to add more Web servers than it is to add more application servers.
This page provides quick links to technical resources and best practices for Rational software. Browse information by product or by technology. Find resources for learning, support, and developer communities.
developerWorks is IBM's technical resource for developers, providing a wide range of tools, code, and education on DB2, eServer, Lotus, Rational, Tivoli, and WebSphere as well as on open standards technology such as Web services, Wireless, Linux, XML, Java technologies, and more. By providing focused and relevant technical information for developers, developerWorks offers choices you can apply to building and deploying applications across heterogeneous systems. Using developerWorks, you can take full advantage of open standards and the IBM Software Development Platform in an on demand world.
This White paper describes how to manually modify certain parts of the WebSphere Application Server Version 5.x configuration that are not available through the administrative tooling that comes with the product. Version 5.x configuration, for all editions of the product, is stored in XML files in a subdirectory under the main product installation root directory.
See also the documentation for the type of application that you are developing, such as Web applications, EJB applications, Web services applications, or applications that use messaging. Many sections contain Web resources for learning topics that bring attention to specific documents that become available.