WebSphere traditional provides a servlet for serving all static content. You must remove any servlet mappings related to static files in the web.xml file, and enable WebSphere static file serving by creating the ibm-web-ext.xml file as shown by the following example in the WEB-INF folder of the application.

				
	<xml version="1.0" encoding="UTF-8"?>
	<web-ext
	    xmlns="http://websphere.ibm.com/xml/ns/javaee"
	    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	    xsi:schemaLocation="http://websphere.ibm.com/xml/ns/javaee http://websphere.ibm.com/xml/ns/javaee/ibm-web-ext_1_1.xsd"
	    version="1.1">
	    
	    <reload-interval value="3">
	    <enable-directory-browsing value="false">
	    <enable-file-serving value="true">
	    <enable-reloading value="true">
	    <enable-serving-servlets-by-class-name value="false">
	    
	</web-ext>
					
			

For WebSphere to serve static files in your application, the fileServingEnabled property must be set to "true". To set this value globally for all Web applications in your WebSphere instance, set the fileServingEnabled custom property in your Web Container configuration through WebSphere's administrative interface. File serving can also be enabled on a per-application basis by setting it in the ibm-web-ext.xml of your Web application archive (WAR). You can use the Extensions tab of the Web Deployment Descriptor editor in Rational Application Developer or the Design tab in the WebSphere Developer Tools in Eclipse to make the update.