WebLogic Server

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:	Oracle WebLogic Server is a Java Enterprise Edition application server platform designed to host distributed applications written using Java and the Java Enterprise Edition frameworks. WebLogic Server has Enterprise Service Bus (ESB) capabilities that can be configured to provide system connectivity and data transformation spanning Information Technology (IT) environments. WebLogic Server Standard and Enterprise Editions are included in this entry.
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 v21.6
Decision Date:	06/11/2021
Aliases:	WebLogic Enterprise; WebLogic Scripting Tool (WLST)
Introduced By:	Extended Tool List (ETL)
Vendor Name:	Oracle

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	Vendor Desupport Date
8.1	07/15/2003	09/30/2009	09/30/2011
9.2	11/28/2006	11/30/2011	11/30/2013
10gR3 (10.3.0.x)	09/01/2008	01/31/2014	01/31/2017
11gR1 (10.3.5.x)	05/16/2011
11gR1 (10.3.6.x)	02/26/2012	12/31/2018	12/31/2021
12cR1 (12.1.x)	12/01/2012	12/31/2016	12/31/2019
12cR2 (12.2.x)	10/01/2015	10/31/2020	08/01/2025
14c (14.1.x)	03/01/2020	03/31/2025	03/31/2028

Current Decision Matrix (06/09/2021)

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 STAT review is conducted and signed by Associate Deputy Assistant Secretary (ADAS), Enterprise Program Management Office (EPMO) or designee and based upon a recommendation from the Strategic Technology Alignment Team (STAT) Working Group (WG), 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

CY2019

CY2020

CY2021

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

10gR3 (10.3.0.x)

Unapproved

11gR1 (10.3.5.x)

Unapproved

11gR1 (10.3.6.x)

Divest
[6, 7]

Divest
[3, 5, 6, 7, 8]

Divest
[3, 5, 6, 8, 9]

Divest
[3, 5, 6, 9, 10]

12cR1 (12.1.x)

Divest
[6, 7]

Unapproved

12cR2 (12.2.x)

Approved w/Constraints
[6, 7]

Approved w/Constraints
[3, 5, 6, 7, 8]

Approved w/Constraints
[3, 5, 6, 8, 9]

Approved w/Constraints
[3, 5, 6, 9, 10]

14c (14.1.x)

Unapproved

Approved w/Constraints
[3, 5, 6, 7, 8]

Approved w/Constraints
[3, 5, 6, 8, 9]

Approved w/Constraints
[3, 5, 6, 9, 10]

Decision Constraints


[1]	Known security vulnerabilities must be properly remediated prior to product deployment. Product must remain properly patched per Federal and Department standards in order to mitigate known and future security vulnerabilities.

[2]	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.

[3]	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.

[4]	As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans approved, may continue to operate this technology. In the case of a project that has implemented, or been approved for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was approved or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.

[5]	Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.

[6]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities.

[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, Microsoft Internet Information Services (IIS), and Oracle Database are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle. This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle. This product can be configured with a MySQL Database which currently has TRM constraints for intranet use only due to its many known security issues. If MySQL is selected for use with this product, these factors should be considered especially when an instance of this product will be considered a Moderate or High Risk system. See the MySQL Database TRM entry for more details.

[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]	Users must ensure that Microsoft Structured Query Language (SQL) Server, Microsoft Internet Information Services (IIS), and Oracle Database are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle. This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle. This product can be configured with a MySQL Database which currently has TRM constraints for intranet use only due to its many known security issues. If MySQL is selected for use with this product, these factors should be considered especially when an instance of this product will be considered a Moderate or High Risk system. See the MySQL Database TRM entry for more details. Users must not use My Structured Query Language (MySQL) Database - Community Editions due to it being unapproved (refer to the ‘Category’ tab under ‘Runtime Dependencies`).

Note:

At the time of writing this version 14c (14.1.1.0.0) is the latest version released on March 1, 2020.

References

The following reference(s) are associated with this entry:
Type	Name	Description
Vendor Provided*	Installation Requirements	This site links to the system requirements for this software.
Vendor Provided*	ORACLE Information Driven Support	Oracle Support Information for Extended support. Depending on your browser you may need to refresh the link to get it to work properly
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Technology Components

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
Java Runtimes (JRE) included with WebLogic	Java Runtimes (JRE) that are licensed with, required for, and supported with a version of WebLogic Server are approved as part of this entry and supersede other TRM decisions on Java for other products and uses. This component approval applies only to the use of JRE for the sole purpose of the support of WebLogic Server.
Oracle WebLogic Server Enterprise Edition	Oracle WebLogic Server Enterprise Edition includes all the features and benefits of Oracle WebLogic Server Standard Edition, Java SE Advanced and Oracle Virtual Assembly Builder.
Oracle WebLogic Server Standard Edition	Oracle WebLogic Server Standard Edition includes Oracle TopLink and Application Development Frameworks, Oracle Web Tier and the core WebLogic Server.
WebLogic Scripting Tool (WLST)	The WebLogic Scripting Tool (WLST) is a command-line scripting interface that system administrators and operators use to monitor and manage WebLogic Server instances and domains. The WLST scripting environment is based on the Java scripting interpreter, Jython. In addition to WebLogic scripting functions, you can use common features of interpreted languages, including local variables, conditional variables, and flow control statements. WebLogic Server developers and administrators can extend the WebLogic scripting language to suit their environmental needs by following the Jython language syntax.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Application Technology Application and Web Server Software	Application Server Software

Operating Systems Supported by the Technology

Red Hat Enterprise Linux (RHEL) - Approved w/Constraints
Windows Client - Approved w/Constraints
Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This technology is supported by a well-known vendor.
This is a mature technology with documentation available.

Adoption Risks

There are other TRM-approved technologies that provide similar functionality.
This technology may be able to store, collect or transmit Personally Identifiable Information (PII), Protected Health Information (PHI) or other sensitive VA data.
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
This technology is available as freeware. If commercial support is not purchased, the product will be without clearly defined support options which may result in suboptimal enterprise level support.
This technology relies on Java Development Kit (JDK) - Oracle, which has a rapid release and update schedule.
There are known High and Critical Common Vulnerabilities and Exposures (CVEs) and VA Network & Security Operations Center (NSOC) vulnerabilities identified for this technology. Users should refer to NVD - Results (nist.gov)

Architectural Benefits

This technology is portable across platforms.

Architectural Risks

The installation program requires a Java run-time environment (JRE) to run. The JRE is in the process of being divested and unapproved on TRM.

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 22.1

General Information

Vendor Release Information

Current Decision Matrix (06/09/2021)

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

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 22.1

General Information

Vendor Release Information

Current Decision Matrix (06/09/2021)

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

Architectural Risks

EMAIL UPDATES