Remedy Application Request System - comprises a server component which is C based. Applications are developed using Remedy workflow on the server. A midtier component connects to server and dependent on config renders jsp's which are deployed to Tomcat. There is a Java API to the Remedy ARS server but other than that it is C as far as I am aware
-----Original Message----- From: Goehring, Chuck Mr., RCI - San Diego [mailto:[EMAIL PROTECTED] Sent: 26 November 2003 22:46 To: Tomcat Users List Subject: OT: RE: Tomcat 4.1.29 and Remedy 5.1.2 MidTier Simon, Just for curiosity, is the Remedy trouble reporting system (don't know the specific name) Java-based? We have some support folks that are running Remedy for the Gov. Thanks Chuck -----Original Message----- From: Simon Taylor [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 26, 2003 12:41 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.1.29 and Remedy 5.1.2 MidTier Ok thanks for the feedback. Ended up reverting to Tomcat 4.0.6 which played better with the midtier. Cheers Simon -----Original Message----- From: Jeff Tulley [mailto:[EMAIL PROTECTED] Sent: 26 November 2003 18:04 To: [EMAIL PROTECTED] Subject: RE: Tomcat 4.1.29 and Remedy 5.1.2 MidTier Yeah, that is mostly correct. There are also places where the spec is vague or doesn't specify behavior, and different application servers implement things differently. There are not a whole lot of spec or operation changes from the 4.0.x series that would completely break you. Offhand I can think of one though: The invoker servlet. It allows you to fire up a servlet directly by class name without defining it in your web.xml. Relying on that is dangerous and does lead to non-portable applications. As of Tomcat 4.1.12, the invoker was disabled by default. But, since you are running a JSP, there is no guarantee that there is a servlet in the mix (unless the JSP is doing a forward to a servlet or something). I think our Remedy team is using the ServletExec, so I do not have any examples myself of how to get it working on Tomcat. And, the full exception does not seem to be of much help. Maybe set debug="99" in the context definition and in all places where debug="0" in server.xml. That might yield a better error message. (Maybe not though). >>> [EMAIL PROTECTED] 11/26/03 2:48:29 AM >>> Hi Jeff, Thanks for the response. I already have a call in with Remedy and postings on the ARSLIST (no value from either so far). The ARSList does not have one posting that states the Midtier can be made to work with Tomcat (even though the doc states it can). Remedy Midtier comes with ServletExec as the default container - but I am loathe to swap Tomcat out as we already use it for other servlets. The support for 5.1.2 on Tomcat is there. Plus we are already running Remedy ARWEB 4.1.1 using Tomcat. I am new to Java, Tomcat and Servlets but have been reading around, Murachs Servlets and Wrox - Professional Apache Tomcat book. If a webapp is built so it doesn't rely on container specific extensions then it should be portable across containers right? Also what might be an obstacle to a webapp running on Tomcat 4.0.x but not on 4.1.x. I have read that these versions support different servlet specifications but aren't they backwardly compatible? On attempting to use Coyote HTTP Connector straight to Tomcat via http://enmc-mic:4321/arsys/apps/shared/config/config.jsp I get:- type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception org.apache.jasper.JasperException at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 54) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2417) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.valves.RequestDumperValve.invoke(RequestDumperValve.java :221) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:193) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:781) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne ction(Http11Protocol.java:549) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:589) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:666) at java.lang.Thread.run(Thread.java:484) root cause javax.servlet.ServletException at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImp l.java:536) at org.apache.jsp.config_jsp._jspService(config_jsp.java:357) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 10) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2417) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.valves.RequestDumperValve.invoke(RequestDumperValve.java :221) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:193) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:781) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne ction(Http11Protocol.java:549) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:589) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool. -----Original Message----- From: Jeff Tulley [mailto:[EMAIL PROTECTED] Sent: 25 November 2003 23:03 To: [EMAIL PROTECTED] Subject: Re: Tomcat 4.1.29 and Remedy 5.1.2 MidTier Our Remedy team gave me a URL for the remedy listserver: [EMAIL PROTECTED] Also, I'd check their web / support site. I cannot imagine that this is not a solved problem and that you would find good support there to get this running. >>> [EMAIL PROTECTED] 11/25/03 3:21:46 PM >>> Here's hoping someone out there has tried to install the Remedy MidTier 5.1.2 with Tomcat 4.1.29. I cant get it to work. :-) I have Tomcat working no problem - running examples and other servlets. I have Apache working into Tomcat using JK no problem running servlets and static. Remedy MidTier doesn't want to play when running config.jsp from Tomcat I get :- javax.servlet.ServletException at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImp l.java:536) at org.apache.jsp.config_jsp._jspService(config_jsp.java:357) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) Any help gratefully appreciated. Simon Simon Taylor Managed Services Technology Consultant Nortel Networks p - 01279 404289 (ESN 742 4289) m - 07740 533743 (ESN 748 3743) e - [EMAIL PROTECTED] "I code therefore I am" Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., The Leading Provider of Net Business Solutions http://www.novell.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., The Leading Provider of Net Business Solutions http://www.novell.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
