Is the goal to put normal HelpDesk/ChangeManagement out on the www? Or - is it the ability to let people outside the web participate in some way as part of a process. (Possibly to initiate a process, do a step of the process review the process)
If - the goal is the 2nd option - I will suggest considering Kinetic Request. It allows you to publish just the capabilities you want to the external www -- in a themed/branded way that works with all common browsers -- and snappy fast too. http://www.kineticdata.com/request.html Let me know if you would like a demo. Thanks, -John On 10/18/07, Den Fong <[EMAIL PROTECTED]> wrote: > > ** I just want to clarify the issue about placing the Remedy app on the > web. > > We need to make the connection as secure as possible, it was proposed to > proxy into our internal system where the Remedy application would sit. So > would a better solution be put a mid-tier instance out in the environment > and have the mid-tier connect into the corp system? Is there any other > security best practices that can be used on the Remedy server/application > itself? > > TIA > > Den > __20060125_______________________This posting was submitted with HTML in > it___ -- John David Sundberg 235 East 6th Street, Suite 400B St. Paul, MN 55101 (651) 556-0930-work (651) 247-6766-cell (651) 695-8577-fax [EMAIL PROTECTED] _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
