Asset ID: |
1-71-2329226.1 |
Update Date: | 2017-11-17 |
Keywords: | |
Solution Type
Technical Instruction Sure
Solution
2329226.1
:
SL3000 - How Java Interacts With ACSLS Library Software
Related Items |
- Sun StorageTek SL3000 Modular Library System
|
Related Categories |
- PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: SL3000-8500 Library
|
In this Document
Created from <SR 3-16187963841>
Applies to:
Sun StorageTek SL3000 Modular Library System - Version All Versions and later
Information in this document applies to any platform.
Contacted the customer to chat about this issue. They have an old version of Java 1.6 running on their ACSLS server that is a security risk.
They are wondering if Java is used with ACSLS.
Goal
Need to know how Java interacts with ACSLS control software.
Solution
The graphical User Interface, surrogate for the GUI does uses Java.
If you do not install the Graphical User Interface, when you installed 8.3 then you can safely delete any Java version you want without effecting ACSLS.
If you are not sure, you can ssh into the ACSLS server as root and at the command line run the following command:
# ps -ef | grep java
root 875 1 0 Nov 14 ? 1:06 /usr/java/bin/rmiregistry 50010
root 958 1 0 Nov 14 ? 2:16 /usr/java/bin/java -Dsurrogate -Dslim.logdir=/export/home/ACSSS/log/sslm -Dslim
^
^
If it shows a Java connection to an ACSLS surrogate, then then Graphical User Interface was installed with 8.3.
The easiest way to get rid of the link is to:
1. Export the acsls database to a safe location.
2. Uninstall ACSLS 8.3
3. Install ACSLS 8.3 again and DO NOT install the Graphical User Interface.
4. Import the ACSLS db back and it should back to full operations again.
Check it again with the ps command. If no link exist, you can safely remove any Java version out there without effecting ACSLS.
References
<NOTE:1013165.1> - ACSLS - How to Gather Diagnostic Logs and Information
Attachments
This solution has no attachment