Java Service Wrapper

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:	Java Service Wrapper (JSW) allows Java applications to be installed and controlled like native Windows services or Unix/Linux daemon processes. This technology includes fault detection software which monitors and reacts to problems. This product has multiple editions. All editions provide basic functionality included in the Professional, Standard, and Community editions. More advanced functionality, such as internationalization and event processing, can be found in the Professional and Standard editions. The assessment for this technology covers all editions of Java Service Wrapper. This technology does not utilize a 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 been assessed by the Section 508 Office and found non-conformant. 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. Please see reference tab for more information concerning product versions.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v22.10
Decision Date:	10/13/2022 at 21:20:25 UTC
Introduced By:	TRM Request
Vendor Name:	Tanuki

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
3.5.11	08/16/2011
3.5.12	09/29/2011
3.5.13	11/02/2011
3.5.14	02/09/2012
3.5.15	06/20/2012
3.5.16	10/26/2012
3.5.17	11/27/2012
3.5.18	04/16/2013
3.5.19	04/19/2013
3.5.20	06/25/2013
3.5.21	09/19/2013
3.5.22	10/11/2013
3.5.23	12/03/2013
3.5.29	03/11/2016
3.5.34	09/27/2017
3.5.35	04/12/2018
3.5.36	09/21/2018
3.5.42
3.5.50

Current Decision Matrix (09/20/2022)

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

CY2017

CY2018

CY2019

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

3.5.22

Divest
[2, 3, 4]

Divest
[2, 3]

3.5.23

Approved w/Constraints
[2, 3, 4]

Approved w/Constraints
[2, 3]

Divest
[2, 3]

3.5.29

Unapproved

Approved w/Constraints
[2, 3]

3.5.34

Unapproved

Approved w/Constraints
[2, 3]

3.5.35

Unapproved

Approved w/Constraints
[2, 3]

3.5.36

Unapproved

Approved w/Constraints
[2, 3]

3.5.42

Unapproved

3.5.50

Unapproved

Decision Constraints


[1]	The open source Community Edition of this product is approved for general use. Use of the Professional and Standard editions of this technology are restricted to projects which require internationalization and/or user-input event processing functionality.

[2]	Use of the Professional and Standard editions of this technology is restricted to projects which require internationalization and/or user-input event processing functionality. This constraint does not apply to the community edition of the technology.

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

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

Note:

At the time of writing, version 3.5.50 is the most current version released.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description

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
No components have been identified for this entry.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Application Technology Development Tools	Build and Deployment Tools

Operating Systems Supported by the Technology

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

Technologies/Standards Relationships

Runtime Dependencies:

No runtime dependencies have been identified.

Comparable Technologies:

FireDaemon Pro

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This technology is mature technology.
At the time of writing, no National Institute of Standards and Technology (NIST) vulnerabilities had been reported and no VA Cyber Security Operations Center (CSOC) bulletins had been issued for the latest versions of this technology.
All editions of JSW provide the ability to set the Windows service priority level at which a JSW wrapped Java virtual machine (JVM) will be run. Priorities may be set to LOW, BELOW_NORMAL, NORMAL, ABOVE_NORMAL, HIGH, and REAL TIME. This capability allows projects to tune applications for improved performance.
JSW Professional edition supports internationalization and language localization. Applications may be internationalized to any language supported by the application platform, or JVM instances may be localized to a specific language.
JSW Professional edition supports the ability to define application events. The technology provides the capability to execute system commands and/or external scripts in response to any application defined event.
All editions of this technology allow Java applications to be installed as either a Windows service or a Unix/Linux daemon process.
This is a well-documented technology.
This technology may improve productivity for specific staff whose responsibilities include the operation of Java applications on windows devices.

Adoption Risks

This technology may have commercial support available at an additional cost.
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.

Architectural Benefits

This technology is compatible with virtual machines, therefore consistent with the enterprise Server Virtualize First Policy (VAIQ 7266972 08-27-2012).
This technology is portable as it runs on multiple VA approved platforms.

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 (09/20/2022)

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 (09/20/2022)

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