This document outlines the changes contained in JAS R2.0 SR3.10. The significant changes are summarized below:
R2.0 SR3.10 now supports use of FIPS 140-2 validated version of OpenSSL (secure socket layer) in the application layer of the system for encrypted communications over TCP/IP. This feature is transparent to the user. In addition, it includes several enhancements to the JAS Administrative Control System (JACS) to support remote processing:
R2.0 SR3.10 provides integration of the remaining error corrections and minor enhancements identified by user change requests and overlays. Appendix B lists those JAS Change Requests (JCRs) addressed in R2.0 SR3.10 that were reviewed and deemed appropriate for integration at this time.
R2.0 SR3.10 provides some new instruments and minor modifications to a few other instruments. Appendix C lists those instrument changes in R2.0 SR3.10.
R2.0 SR3.10 has several new or modified HCI screens that either accommodate new functionality or provide enhanced usability. Most new functionality focus around JAS System Administration, Run Definitions, CAS Planning, Preassigned Mission Planning, Air Defense System, SCL Editor, JAOP Target Area Graphics, and the Video Playback tool.
R2.0 SR3.10 introduces changes to the data model necessary to support the new functionality. Scenario transformation and scenario import/export features provide support for transitioning existing scenarios to the new data model. New in this Service Release is the movement of the data dictionary from a separate table and imbedding the information into the data objects. This means that users no longer need to manually update their input data tables in their JAR. The table structure is automatically updated upon selection of the export function. See Section 9 for additional details. Appendix C contains a list of database and data model changes implemented in R2.0 SR3.10.
Every database change introduced in R2.0 SR3.10 has a corresponding software change in the Import/Export functions and scenario transform function designed to assist the user in upgrading prior scenario data to meet R2.0 SR3.10 requirements. Of particular interest is the method for determining which sensors are “on” has changed and is handled by the transform function. (See Section 3.3 for additional information.)
Also new with this release is the ability to “Archive” run output data (collected Instruments) for a given run. Run output stored in Oracle in BLOB format can be exported to a set of files stored in a user specified folder, and imported back into Oracle. User may then export the output to a JAR for post-analysis. Users may also use a compression application, like WinZip, to compress the exported files. These exported files are in specific Oracle file types and should not be altered in any manner (e.g. no file name changes) or the re-import will not function properly.