The Tomcat issue was resolved beginning w/ v 8.0.33.Ħ Supported on 32 & 64 bit operating systems. There is a known issue with this version that will cause problems with Unanet reports. The Express version has a number of limitations which may prevent its use in your environment.ĥ Important: Avoid use of Tomcat v8.0.32. Additionally, our recommendation is to set the Oracle parameter 'optimizer_adaptive_features' to false when using 12.1.0.2 version.

We are aware of customers successfully operating in Azure, however, we have yet to include this in our testing procedures.ģ Due to issues identified during our testing for 12cR2 on Linux OS, we recommend using the specific version of 12.1.0.2 (12cR). Supported Cloud Platforms - we include AWS in our testing procedures. Supported Virtual Environments - we include Hyper-V and VM-Ware in our testing procedures. Popup Blockers: will need to be configured to allow popups from your Unanet site.Ģ Supported on 32 & 64 bit operating systems. In particular though, the browsers must be configured to allow cookies and javascript. Microsoft SQL Server 2008, 2012, 2014 (Enterprise, Standard, Express Editions where available)ġ Unanet supports the latest supported versions of the listed browsers.īrowser Configuration: The default settings for most browsers is sufficient to use Unanet. Microsoft SQL Server 2008, 2012, 2014, 2016 (Enterprise, Standard, Express Editions where available) Microsoft SQL Server 2008, 2012, 2014, 2016, 2017 (Enterprise, Standard, Express Editions where available) Microsoft SQL Server 2012, 2014, 2016, 2017, 2019 (Enterprise, Standard, Express Editions where available) But I am not sure about this point.Following is a list of versions and the components that are supported in those versions. It appears these two downloads are somewhat mutually exclusive in the sense that if I download and install the 32-bit/64-bit Windows Service Installer version and the 64-bit Windows zip file the startup.bat file in the 64-bit Windows zip file version will not run or interact with the 32-bit/64-bit Windows Service Installer tomcat instance. Remember I am a neophyte when it comes to tomcat and web servers.

Decompress the Tomcat archive file: Rename the apache-tomcat- directory and move.

Then all the above answers make sense and are rather trivial. 5.1 Tomcat Installation Steps Download and install a supported JDK. This zip file has all the common startup/shutdown scripts, batch files for windows, including catalina.bat/.sh etc. I did not realize there was a separate download the 64-bit Windows zip file that has a tomcat server and all the standard array of cmd line tomcat management tools. It is probably evident to anyone with a shred of experience with services and such. I am embarrassed to say how simple it is. So nearly all the answers I have perused were not immediately applicable as many said, 'go to bin and issue the startup.bat file' I am a neophyte but not so much to not be able to look into the bin and start such a file it is existed!įor my simple purposes (again remember that I am a neophyte at tomcat and even web servers) all I wanted to do was to be able to startup and shutdown the tomcat server from a cmd prompt window. With this setup I had some frustrations as setting parameters is done via the gui widget - very helpful I might add. And no %CATALINA_HOME% or %TOMCAT_HOME% etc.

My colleagues were surprised that I did not have a catalina.bat etc. The bin that is created for that download is small - only 4 files. I only downloaded the 32-bit/64-bit Windows Service Installer. I did not have a startup.bat or any bat files. In particular I don't work with services too much. I consider myself somewhat proficient user of windows, but I guess not proficient enough. Even more I am rather new to web servers in general. I ran into the same issue and it was likely due to a combination of being a complete neophyte when it comes to tomcat.

There are a lot of answers here, but many overlook a few points.

Apache tomcat on windows 2008 r2