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 19.3

Apache ActiveMQ
Apache ActiveMQ 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 ActiveMQ (message queue) is a lightweight, open source message broker that allows applications to connect and scale through a common platform for sending, receiving, and temporarily storing inter-application messages between distributed systems. ActiveMQ fully implements the Java Message Service (JMS) Application Programming Interface (API) that allows application components based on the Java Platform Enterprise Edition (Java EE) to create, send, receive, and read messages and enables communication that is loosely coupled and asynchronous.

This technology supports several Structured Query Language (SQL) databases for message persistence, but does not require a database for implementation. Message commands are written to a transactional journal which consists of rolling data logs and the messages themselves are persisted in the data logs of the journal with references to their location being held by a reference store for fast retrieval.
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 Section508@va.gov.
Decision: View Decisions

Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v19.3
Decision Date: 03/05/2019
Introduced By: TRM Request
Vendor Name: Apache Software Foundation (ASF)
- The information contained on this page is accurate as of the Decision Date (03/05/2019).