This week's book giveaway is in the OO, Patterns, UML and Refactoring forum.
We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line!
See this thread for details.
The moose likes Websphere and the fly likes Tip - WebSphere Clustered Environment -  IHS Static Data. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

JavaRanch » Java Forums » Products » Websphere
Bookmark "Tip - WebSphere Clustered Environment -  IHS Static Data. " Watch "Tip - WebSphere Clustered Environment -  IHS Static Data. " New topic

Tip - WebSphere Clustered Environment - IHS Static Data.

Patrick Finnegan
Ranch Hand

Joined: Mar 05, 2002
Posts: 179
In a WebSphere clustered environment there are usually multiple IHS(IBM derivative of Apache) servers set up to spray requests across a couple of Websphere Application Servers. This architecture assumes that the application static content(image files, html etc.) is deployed to the IHS boxes i.e it is not contained in the EAR file that is deployed on WebSphere. However the default WebSphere installation sets up WebSphere to serve static content and in this scenario IHS forwards all requests to WebSphere i.e it's redundant. In fact you can un-install IHS and configure WebSphere to listen on port 80. However IHS is a much more efficient file server and in a production environment it recommended that IHS serve static data. Hence if you bundle everything into the EAR file this won't happen and performance will suffer. I realize that the J2EE spec recommends that EAR files are self contained but if you want performance then separate static data.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link:
subject: Tip - WebSphere Clustered Environment - IHS Static Data.
It's not a secret anymore!