Attention A T users. To access the menus on this page please perform the following steps. 1. Please switch auto forms mode to off. 2. Hit enter to expand a main menu option (Health, Benefits, etc). 3. To enter and activate the submenu links, hit the down arrow. You will now be able to tab or arrow up or down through the submenu options to access/activate the submenu links.

VA Technical Reference Model v 22.8

Apache TomEE
Apache TomEE Technology

General InformationGeneral Information help

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website: Go to site
Description: Apache TomEE is an Apache Java Enterprise Edition Web Profile certified stack in which Apache Tomcat is primarily used. Apache TomEE is assembled from a base version of Apache Tomcat zip file.

There are three different versions of Apache TomEE available: Webprofile, Java application programming interface (API) for RESTful Web Services, and Plus. Webprofile provides the smallest distribution and is fully Java Enterprise Edition Web Profile compliant. Java API for RESTful Web Services builds on Web Profile, adding Java API for RESTful Web Services support, and is also Web Profile certified. The plus package provides all the features for TomEE that are available, including Java Message Service, Java API for Extensible Markup Language Web Services and Java Enterprise Edition Connector Architecture.

This TRM entry covers all the versions of Apache TomEE listed above.
Technology/Standard Usage Requirements: Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information: This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at
Decision: View Decisions

Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v20.6
Decision Date: 06/26/2020
Introduced By: TRM Request
Vendor Name:
- The information contained on this page is accurate as of the Decision Date (06/26/2020).