I have an application deployed using the native WAS Web Server. Is there any way I can set the default index (ie htaccess) for my context root to automatically pick up the index.html in my build?

Eg:If I visit localhost:9080/website I get nothing.

If I visit localhost:9080/website/index.html i get my desired page.

I need to visit the first and get the second.

Is  there a reason why you're bypassing the web server (IHS it sounds like) and using the internal web server built in WebSphere?  Did you intend on your users/ services accessing the app using the server & port combination?

If you use a web server and define the default doc, you can easily redirect to the page you want.

Just curious.

Never tried this before but maybe create an index.htm and put a meta refresh in to index.html

Restart app server and hope and pray that it works.  I'm assuming here that index.htm is the default for direct app server access.

But I have to wonder why your not using IHS?  Wouldn't be an issue if you were.

We leverage Microsoft IIS for the web teir as we also run numerous .net applications.  When you consider the low overhead of the plugin and minimal processing it actually does, this gave us the oppertunity to offload all web server functionality onto sepperate servers.  This gives us an environment where all WebSphere apps are on dedicated WebSphere servers and all Web Applications (plugin included) are on their own dedicated servers.