Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

BusinessWare

General Information

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:	BusinessWare is a technology designed for integrating complex transaction and process-based applications. BusinessWare combines broad capabilities for application integration with Business Process Management (BPM) and Business-to-Business (B2B) integration, providing a unified solution for modeling, implementing, monitoring, and managing end-to-end processes that span multiple systems and organizations. BusinessWare is compatible with the following relational databases to store data: Microsoft Structured Query Language (SQL) Server, DB2, and Oracle Database.
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 v24.4
Decision Date:	04/03/2024 at 13:17:44 UTC
Introduced By:	Extended Tool List (ETL)
Vendor Name:	Vitria

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date
3.1.7	05/13/2002	11/11/2004
4.2	11/11/2003	12/13/2005
4.3.x	12/13/2004	03/01/2009
4.4.x	03/01/2008	01/26/2011
4.5.x	01/26/2010
4.6.x
4.7.x	08/15/2018
4.8.x

Current Decision Matrix (04/01/2024)

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.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2023

CY2024

CY2025

Future>

Release

3.1.7

Unapproved

4.2

Unapproved

4.3.x

Unapproved

4.4.x

Unapproved

4.5.x

Unapproved

4.6.x

Unapproved

4.7.x

Approved w/Constraints
[5, 11, 12, 13]

Divest
[5, 13, 14, 15, 16]

Divest
[5, 14, 15, 16, 17]

Divest
[5, 15, 16, 17, 18]

Unapproved

4.8.x

Unapproved

Approved w/Constraints
[5, 13, 14, 15, 16]

Approved w/Constraints
[5, 14, 15, 16, 17]

Approved w/Constraints
[5, 15, 16, 17, 18]

Decision Constraints


[1]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[2]	In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process.

[3]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[4]	This product is no longer approved for information technology (IT) projects that are or will be mandated to follow standardized processes and tools governing IT activity critical to VA`s implementation of the Veteran-focused Integration Process (VIP).

[5]	Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities.

[6]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[7]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[8]	Users must ensure that Microsoft Structured Query Language (SQL) Server and Oracle Database are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology must use the latest version of Java Development Kit (JDK) - Oracle. Per the Initial Product Review, users must abide by the following constraints: This product is a customized business process and planning resource, nothing is installed on VA computers until systems and processes are identified and the Vitria solution is developed and provided to VA. Security concerns should be addressed as development of solutions takes place. System Owners and Integrators should ensure FIPS 140-2 validated encryption is being utilized when processing PHI/PII.

[9]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[10]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[11]	Users must ensure that Microsoft Structured Query Language (SQL) Server and Oracle Database are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology must use the latest version of Java Development Kit (JDK) - Oracle. Per the Initial Product Review, users must abide by the following constraints: This product is a customized business process and planning resource, nothing is installed on VA computers until systems and processes are identified and the Vitria solution is developed and provided to VA. Security concerns should be addressed as development of solutions takes place. Vitria BusinessWare will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information.

[12]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500.

[13]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[14]	Users must ensure that Microsoft Structured Query Language (SQL) Server, Apache Tomcat, Google Chrome, Microsoft Edge, MySQL and Oracle Database are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology must use the latest version of Java Development Kit (JDK) - Oracle. Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM. This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle. Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details. This technology should not be used with Open Java Development Kit (OpenJDK) as it is unapproved for use at this time. There are other approved java environments available. See Category tab for details. The File Transfer Protocol (FTP) features of this software must not be used as the FTP protocol is prohibited for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services) Per the Initial Product Review, users must abide by the following constraints: This product is a customized business process and planning resource, nothing is installed on VA computers until systems and processes are identified and the Vitria solution is developed and provided to VA. Security concerns should be addressed as development of solutions takes place. Vitria BusinessWare will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information.

[15]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500.

[16]	If this product uses a MySQL database, the product must be configured with a commercial edition of the MySQL Database, which currently has TRM constraints limiting its use for intranet and non-sensitive data only due to its many known security issues. If a commercial edition of MySQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See MySQL Database – Commercial Edition TRM entry for more details.

[17]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 or its successor to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes.

[18]	Users must ensure that Microsoft Structured Query Language (SQL) Server, Google Chrome, Microsoft Edge, MySQL and Oracle Database are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology must use the latest version of Java Development Kit (JDK) - Oracle. Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM. This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle. Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details. This technology should not be used with Open Java Development Kit (OpenJDK) as it is unapproved for use at this time. There are other approved java environments available. See Category tab for details. The File Transfer Protocol (FTP) features of this software must not be used as the FTP protocol is prohibited for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services) Per the Initial Product Review, users must abide by the following constraints: This product is a customized business process and planning resource, nothing is installed on VA computers until systems and processes are identified and the Vitria solution is developed and provided to VA. Security concerns should be addressed as development of solutions takes place. Vitria BusinessWare will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information.

Note:

At the time of writing, version 4.8.0.2 is the most current version, released 04/27/2023.

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
Apache Tomcat	This technology comes bundled with Apache Tomcat version 10.
Vitria Health Level Seven (HL7) for BusinessWare	This module provides a method for generating BusinessWare events that represent HL7 messages from incoming byte streams. This page requires a login.
Vitria Record Mapper for BusinessWare	This module is used to add records to a target system and update database tables.
Vitria Relational Database Management System (RDBMS) Connector for BusinessWare	This module provides a method for connecting to TRM-approved relational databases for data gathering and storage.
Vitria Socket Connector for BusinessWare	This module is used to manage connection requests.


Application Technology Development Tools	Process Management Tools

- The information contained on this page is accurate as of the Decision Date (04/03/2024 at 13:17:44 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (04/01/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (04/01/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

EMAIL UPDATES