OnDemand User Group

Support Forums => OD/WEK & JAVA API => Topic started by: Nolan on June 21, 2018, 07:14:39 AM

Title: ODWEK CGI :(
Post by: Nolan on June 21, 2018, 07:14:39 AM

Yes, we still are using the CGI.  :(

We are trying to move to a Windows 2016 server but are not able to get anything out of the CGI.  Has anyone tried to use the CGI on a Win2016 server?  Even the tracing is not opening a trace file.

Also tried to start up IIS to see if that would help debug the issue but it has not been successful either, any tips there would be helpful too.

Installed V9.5.0.10 of CMOD

Thanks

Title: Re: ODWEK CGI :(
Post by: Justin Derrick on June 21, 2018, 12:54:29 PM

You may need to finally let go of the CGI.  :\

ODWEK provides so much more flexibility and performance though.  :)

-JD.

Title: Re: ODWEK CGI :(
Post by: Nolan on June 21, 2018, 01:00:56 PM

Resolved with a PMR.   Apparently with 9.5 you need to use the default path.  They had installed ODWEK to a different path. 

Updated the default arswww.ini and away we go!

And yes, I have already advised them to get off this old old old CGI!

Cheers

Title: Re: ODWEK CGI :(
Post by: Justin Derrick on June 21, 2018, 02:14:05 PM

If it makes you feel any better...  You're by no means alone!  I've been nagging customers to rebuild their old CGI-based apps for ages.  I believe it's unsupported in v9.5 and absent in v10.1 -- so apply that as pressure.  :)

Take care...

-JD.