Java 1.4.02
General InformationTechnologies must be operated and maintained in accordance with Federal and Department security andprivacy policies and guidelines. More information on the proper use of the TRM can be found on the.Website:Description:Java Enterprise Edition (Java EE) is an enterprise application deployment platform standard.Java EE leverages universal standard, platform and Application Programming Interfaces (APIs) that facilitate the writing, development, deployment, and management of multi-tier, server-centric applications. The Java EE standard is used for offloading common infrastructure tasks through its container-based infrastructure. The standard uses the object-oriented Java programming language and it extends the Java Platform, Standard Edition (Java SE). Note: This is a standards entry and does not itself expressly approve software. Please see the related technology entries for approved software that may be installed.On September 12, 2017, Oracle Corporation announced that it would submit Java EE to the Eclipse Foundation. Jakarta, Enterprise Edition (Jakarta EE) is the standard in community-driven enterprise specifications supported by the Eclipse Foundation.
The Eclipse Jakarta EE Platform project produces the Jakarta EE platform specification, which is an umbrella specification that aggregates all other Jakarta EE specifications. Jakarta EE editions are not covered by this TRM entry because Jakarta EE is under a new management structure. Jakarta EE will need to be reviewed and approved under its own and separate TRM entries.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:Decision Source:TRM Mgmt GroupDecision Process:One-VA TRM v19.8Decision Date:Aliases:Java EE; Java Platform; Java Platform Enterprise Edition, Java EE 7, Jakarta EEIntroduced By:Extended Tool List (ETL)Standards Body. Note: This list may not be complete. No component, listed or unlisted, may be used outside ofthe technology in which it is released.
2.00Please checkfor the latest firmware upgrades for your products. The latest issues and known issues for Command View ESL and the Interface Manager can be found on the web at:New Features in this Release: SDLT 600 Drive Support: The SDLT 600 drive is now fully supported by both Command View ESL and the Interface Manager.
Please make sure to upgrade the Interface Manager to version I142 before installing the SDLT 600 drives in an existing library.Fixed in I142/1.4.02: Using HP web services to determine the optimal firmware updates for your library would fail to download firmware files for certain proxy configurations.Fixed in I141/1.4.01: Dual-SAN configurations caused a reboot required condition on the Interface Controllers. Rebooting the Interface Controllers would not clear the condition. This could have caused backup failures due to automatic reboots of the Interface Controllers. Performing a firmware download in Command View ESL would occasionally 'hang' and would not complete. Barcode information reported on the Inventory and Media Management page was not always displayed correctly.Fixed in I140/1.4.00: Drive communication failures on e2400-FC Interface Controllers have been resolved.
One or more messages may still appear in the Event Log regarding communication issues when backups are occurring - this is normal? But external (host) communication with the drives has been resolved.
When the 'create host' command in the command-line interface was used with a hostname, the hostname was not kept. Managing multiple libraries in Command View ESL would occasionally fail. Each entry in the Library Selection page would lead the user to only one of the libraries. This would make the other libraries unmanageable. The compass of terrestrial directions vol. iii the east pdf book. After setting the Interface Manager IP address with an IP in the range 1.1.x.x, the Interface Manager was unresponsive.
After installing an e2400-FC Gb Interface Controller, the Interface Manager was unresponsive (this issue was actually fixed in I130). After setting the Interface Manager's IP address to a static address, the address changed back to a DHCP address. This usually occurred after a reboot of the Interface Manager but was known to occur at other times. After running the 'restore system config' command in the command-line interface, the user saw the command prompt even though the Interface Manager was in the process of rebooting. The command line appeared unresponsive. The 'Edit Custom Device Map' dialog in Command View ESL could become unresponsive when clicking the 'OK' button.Known Issues. Symptom: When downloading firmware to a 2-unit ESL library, the command line interface will indicate that the firmware download is complete, but the library is not ready.Solution: At that time the firmware download is complete to the master library, but it can take up to 1 hour for the slave library to receive the firmware.
The firmware download to the slave library is done when the front panel on the slave library is operational.THE DHCP SERVER, ON A PRIVATE LAN, CAN CAUSE NETWORK CONFIGURATION ISSUES. Symptom: All of the network ports, except the one labeled 'NETWORK,' support a private LAN used to communicate with the interfaces. This private network has a DHCP server to server up IP configurations to the interfaces. If this network is connected to a LAN, it will attempt to serve up IP configurations to DHCP clients on the LAN, potentially causing issues for those clients. The Interface Manager will also attempt to manager other interface controllers that it finds on the LAN.Solution: Make sure that only the 'NETWORK' port on the Interface Manager is plugged into the public LAN.DRIVES THAT ARE OFFLINE OR NOT SEEN BY THE INTERFACES MAY CAUSE AN INTERNAL INTERFACE MANAGER ERROR 101.
Symptom: The CLI may respond to a command with the following statement: 'The interface Manager is busy and can't execute the selected command. Please try again in a few minutes.' Solution: This could occur if the Interface Manager is re-discovering the library configuration. If this response continues after several minutes, execute the CLI command 'show library status' to determine if there was an issue discovering the library configuration.ERROR 1722 WHEN TRYING TO INSTALL JAVA FROM THE MANAGEMENT STATION. Symptom: When a client tries to install the Java Runtime Environment provided by the Management Station the installer complains about 'Error 1722.' The installation fails and Command View ESL cannot be loaded.Workaround:There are two known workarounds:1.
When presented with the 'Plugin Info' page while loading Command View ESL, select the option 'Download and install from the Sun website' to install Java on the client from the Internet instead of from the Management Station.2. Attempt to install Java on the client again using the same method. This will detect the previous installation attempt and ask if you want to remove or repair the previous installation? Remove it.Install the following patch on the client (for Windows XP systems):The client can then proceed with installing Java from the Management Station.LICENSES SHOW UP IN THE 'UN-MANAGED LICENSES' SECTION OF THE LICENSE KEY SUMMARY TAB. Symptom: The Event Log may contain messages regarding drive and robotics communication errors. These messages generally refer to communication between the Interface Manager and those devices?
Not host communication. These messages occur more frequently during periods of high backup activity. If hosts are still able to communicate with the devices, then you should not be concerned. The Interface Manager should re-establish communication with those devices within 15 minutes.DOWNGRADING INTERFACE CONTROLLER CODE WITH PARTITIONS TURNS STATUS TO CRITICAL.
Symptom: Downgrading Interface Controller code below the minimum version required for partitioning (version 5.6.06) will invalidate the partition configuration. The partition configuration cannot be seen by external hosts and the library status will be critical. This may also be seen when installing a replacement Interface Controller card that has a firmware version below 5.6.06.Workaround: Please upgrade the Interface Controllers to the minimum required version (version 5.6.06) to restore the partitions.WORLD WIDE PORT NAMES ARE NOT DISPLAYED PROPERLY. Symptom: When partitions are defined for an ESL E-Series library, the ability to modify the Load Port configuration from the operator control panel is disabled.Workaround: Load Port configuration cannot be modified when partitions are defined. If you wish to modify the Load Port configuration, use Command View ESL to remove all of your partitions. The ability to modify the Load Port configuration should be enabled. If not, please add back a single partition and then immediately remove it.
Load Port configuration from the operator control panel should then be enabled.CANNOT VIEW INVENTORY OR PARTITIONING PAGES IN COMMAND VIEW ESL DUE TO ERROR. Hewlett Packard Enterprise Development shall not be liable for technical or editorial errors or omissions contained herein. The information provided is provided 'as is' without warranty of any kind. To the extent permitted by law, neither HPE nor its affiliates, subcontractors or suppliers will be liable for incidental, special or consequential damages including downtime cost; lost profits; damages relating to the procurement of substitute products or services; or damages for loss of data, or software restoration. The information in this document is subject to change without notice. Hewlett Packard Enterprise Development and the names of Hewlett Packard Enterprise Development products referenced herein are trademarks of Hewlett Packard Enterprise Development in the United States and other countries. Other product and company names mentioned herein may be trademarks of their respective owners.Legal Disclaimer: Products sold prior to the November 1, 2015 separation of Hewlett-Packard Company into Hewlett Packard Enterprise Company and HP Inc.
Java 1.4.0 Download
May have older product names and model numbers that differ from current models.