Hi All,
Please disregard the previous email. I ran a lot of comparing between Dev's
original files, and those included with the patch, and found the answer to this.
Mid-Tier determines what default web pages are, not through IIS, or
ServletExec, but through Mid-Tier's web.xml file, located within the WEB-INF
folder. I added the following toward the bottom of the file, and recycled
Mid-Tier, and this is working fine now:
<welcome-file-list>
<welcome-file>index.html</welcome-file>
<welcome-file>home</welcome-file>
</welcome-file-list>
Looking at the readme file that came with Patch 21, it seems web.xml has been
replaced as part of every patch, since Patch 1.
I will make a note this in our internal release process, so this should not be
a problem for any future patches we may run.
Eric
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED]
Behalf Of Eric Cleereman (IT)
Sent: Thursday, March 01, 2007 11:13 AM
To: [email protected]
Subject: Default Files in Mid-Tier
**
Hi All,
My environment on my development Mid-Tier server is now as follows:
Windows 2000, SP4, all patches
IIS
Java Sun 1.6.0-b105 (JDK)
ServletExec ISAPI 5.0.0.13
Mid Tier 6.03.00 patch 21
Windows, ServletExec, Java, and Mid-Tier were all patched in a short span of
time. Mid-Tier seems to be working as far as serving Remedy content goes, and
the Daylight Saving times calculate correctly.
The problem I am now having is that default web pages such as "index.html"
error out within Mid-Tier. As an example, http://remedydev/arsys generates the
following error:
ARERR [9217]
File not found. Either the file requested is not present or the URL
supplied is bad.
http://remedydev/arsys/index.html displays the content in a file on the server
called index.html.
We use the an IFrame within the index.html file. This IFrame uses 100% of the
window. This allows users to hit Mid-Tier using a shorter address. It
maintains that address throughout the user's Remedy session, which effectively
prevents users from creating bookmarks. It also allows several JavaScripts
encoded in our page headers to dynamically size the browser to fit the content,
print from that content, and all sorts of other bells and whistles which we'd
like to keep.
When looking at either of our unpatched production servers, http://remedy/arsys
displays the same content as http://remedy/arsys/index.html, and not an error.
I've double checked that index.html exists within the same folder structure on
both Dev and Prod, that the files' content is identical, and that the
permissions match. I've also checked in IIS, under the properties for both the
Default Web Site and the Scripts virtual directories, and on both Dev and Prod
it has Default Documents enabled, and index.html listed as the first default
document.
I suspect (but am not positive) that the problem lies within either IIS or
ServletExec, neither of which are my forte. Any suggestions on how to get
default web pages displaying again would be much appreciated.
Eric Cleereman
__20060125_______________________This posting was submitted with HTML in it___
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
