Design applications

 

+

Search Tips   |   Advanced Search

 

 

Overview

  1. Study and implement bundled sample applications.

  2. Consult the architectural suggestions in Application design consideration.

  3. Consult the following Web resources for learning.

    The top 10 (more or less) J2EE best practices

    The authors, which 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.

    IBM Patterns for e-Business

    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.

    WebSphere Best Practices and Performance Considerations

    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.

    Best practices for using XSLT in WAS applications

    The author states: In this article I explore the reasons why some WAS applications use XSL for HTML production instead of 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 WAS 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 WAS uses of XSLT, such as XML-to-XML transformations and XML-to-text transformations.

    Best practices for using WAS Web services

    The author states: Web services performance comes of age in WAS V5.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 WAS 5.0.2. I will examine the performance of WAS 5.0.2 Web services and establish some best practices for optimizing Web services performance on WebSphere Application Server 5.0.2

    WAS V5 Tech

    Note: Separating Static and Dynamic Web Content

    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 your static Web content (HTML, GIF, CSS files, and so on.) and dynamic Web content (servlets and JSP files) allows processing capacity to be split between the Web server and application server. We 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.

    WebSphere best practices on developerWorks

    The WebSphere Best Practices Zone provides a collection of best practices for administering WAS. Over time this zone will grow to include best practices for using other WebSphere software products, and to cover more topics.

    Rational on developerWorks

    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 main page

    This page is the entrance to IBM's resource for developers.

    Resource reference list

    WAS has a large amount of existing documentation. Use the following information as a guideline to find the documentation that you require.

    User communities and other non-IBM sites

    These sites gather knowledge about using WebSphere products.

WAS V5.x best practices for configuration changes

This White paper describes how to manually modify certain parts of the WebSphereŽ Application Server V5.x configuration that are not available through the administrative tooling that comes with the product. V5.x configuration, for all editions of the product, is stored in XML files in a subdirectory under the main product installation root directory.

 

What to do next

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.


 

See Also


J2EE specification
WebSphere applications