Hmmm... flushed the cache several times over the past couple hours. I've found, however, that doesn't change anything unless I also close and reopen the browser. But that's a rant for another time. The user definitely has permissions to the app and forms within. Besides, this issue is before the login, so technically, there's no user yet. There have been no changes to the app or forms. In this case I'm using direct access to the app, not a home page.
-Aaron * Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza Sent: Wednesday, May 16, 2007 10:51 AM To: [email protected] Subject: Re: custom login.jsp per application ** Aaron, Check the following: 1) Have you renamed the home page to something else and not flushed the mid-tier cache? 2) Have you renamed a view of the home page that has that has to be displayed? (It may not be this as usually if the view has been renamed or doesn't exist, the system shows you the default admin view.) 3) Does the user have permissions to the form? (I do not think it might be a permissions related issue as the error would have been slightly different, but doesn't hurt checking) Login.jsp is not really a ARS form. Its just a mid-tier login page, so whatever form you might try to access, using either direct access or the regular login that takes you to the home page, the first page that you get redirected to before you login is the login.jsp page.. Your issue is not the login.jsp page but the opening of the home page. The name of the home page does not match the cached name of the page.. Flushing your mid-tier cache should pretty much resolve your issue. Rgds Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Aaron Keller Sent: Wednesday, May 16, 2007 10:18 AM To: [email protected] Subject: custom login.jsp per application ** We have several web apps, and users of one of them would like to see a login page that is different from the others. Seems simple enough, and I'm sure I'm missing the obvious. Any suggestions? We're running 6.3 server and mid-tier, on solaris The 6.3 docs say very little - basic guide p.453 says: >>Example 2: Login with customized login page >>http://<mid_tier_server>/arsys/apps/<ar_server>/<app>/ >>login.jsp?goto=<URL>&server=<server_name> >>The user logs in using a login page customized for an application, and then >>goes to the specified URL. But when I do the above I get the default login.jsp (http://<mid_tier_server>/arsys/shared/login.jsp) and if I then login I get "ARERR 303, Form does not exist on server: login.jsp" - as if the "login.jsp" is a form alias. Here's what I've tried: -adding the customized login.jsp and login_common.jsp to the App's Support Files page (in the Admin tool, App properties) under the top directory and in the Resources directory -actually creating the directory /apps/<ar_server>/<app> and depositing the login.jsp and login_common.jsp there thanks in advance- -Aaron * Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> SunCom is the wireless company that's committed to doing things differently. Things we want you to know. This e-mail and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. This communication may contain material protected by the attorney-client privilege. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ SunCom is the wireless company that's committed to doing things differently. Things we want you to know. This e-mail and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. This communication may contain material protected by the attorney-client privilege. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
