Achieving Dojo loading optimization across various IBM WebSphere Portal themes

This article shows how to achieve Dojo loading optimization across various IBM WebSphere Portal themes to improve performance of Portal applications.

This popped into my blog-roll today, and I thought it worthy of being re-posted.

Table of Contents

• 1 Introduction

• 2 Understanding Dojo packaging in themes

• 3 Determining which Dojo modules your application needs

• 4 Adding the identified modules to the theme profile

• 5 Capability filters

• 6 Conclusion

• 7 Tell us what you think

• 8 Resources

• 9 About the author

Introduction

Dojo is bundled as part of the IBM® WebSphere® Portal theme and can be used by any portlet application running in Portal. Typically if portlet applications use any Dojo features, they rely on Dojo being loaded by the theme when run in Portal rather than packaging the Dojo in the portlet .war file. 

However, for improved performance, it is important to load Dojo resources in an optimized way by combining multiple files into a single request rather than multiple requests for each individual Dojo file/resource. This article focuses on how to achieve this optimization across various themes and Dojo versions in Portal.

Achieving Dojo loading optimization across various IBM WebSphere Portal themes

Whilst you're on the track of those annoying little performance problems, I'd also strongly recommend Steve Souders' book - High Performance Web Sites - and his series of articles - Best Practices for Speeding Up Your Web Site - which includes: -

• Minimize HTTP Requests
• Use a Content Delivery Network
• Add an Expires or a Cache-Control Header
• Gzip Components

etc.