Solaris Easy Access Server 3.0 Release Notes

Chapter 6 Late-Breaking Documentation Issues

This chapter lists errors in the Solaris Easy Access Server 3.0 documentation, or the documentation for any of the Solaris Easy Access Server products. It also lists documentation that was not listed in "Accessing Online Documentation" in Solaris Easy Access Server 3.0 Installation Guide.

Solaris Easy Access 3.0 Installation Guide

The following sections describe errors in the SEAS 3.0 Installation Guide.

Solaris 2.7 References

Throughout the SEAS 3.0 Installation Guide the manual contains references to Solaris 2.7.

Solaris 2.7 is now referred to as Solaris 7.

Availability of the SEAS 3.0 Documentation [4252420]

The Preface states that the SEAS 3.0 Installation Guide is available on the SEAS documentation CD as an AnswerBook2 document and as a PostScriptTM file and PDF file. Please note that the PostScript and PDF formats are available on the SEAS product CD.

In Chapter 4, "The SEAS Documentation" states that all SEAS documentation is available on the SEAS documentation CD, except for the Release Notes which are available in printed form.

The correct statement is that all SEAS documentation is available on the SEAS 3.0 documentation CD except the Release Notes. The release notes for the SEAS 3.0 components are available on the SEAS 3.0 product CD in various formats, but they are not available in printed form.

Uninstalling Using the jre Command [4252420]

The example of the uninstallation command shown in the section "Uninstalling Using the jre Command" in Chapter 2 is incorrect. The correct command should read as follows:

jre -cp /var/sadm/prod/com.sun.DiskSuite/60790009 uninstall_DiskSuite_4.2

Using autorun.exe to Install SEAS Clients on PCs [4252420]

Steps 3 and 4 in the procedure on how to install SEAS clients over the network in Section "Performing Client Software Installations" in Chapter 3 specify to find and double-click the Installer icon. This is incorrect. The file to find and double-click is autorun.exe.

SMC Cannot Be Installed on PCs Running Windows

The section on "Client Installations" in chapter 3 incorrectly states that the Solaris Management Console can be installed on PCs running Windows. This is incorrect. The SMC can only be installed in a Solaris operating environment.

Using the ab2cd Command to Run AnswerBook2 Server [4252420]

Step 3 of the procedure on how to run the AnswerBook2 Server is incorrect. The correct command to use is ab2cd.

Availability of Binary Code Licenses

Table 5-1 in Chapter 5, Licensing, states that for DiskSuite 4.2 and JDK 1.1.7 you get one machine license and refers you to the online Binary Code License. This is incorrect. The Binary Code License is a printed document that ships with the SEAS 3.0 product. The license is not available online.

Sun WebServer 2.1 Supports HotJavaTM and NetscapeTM as Browsers

The Product Compatibility table in Appendix B states that HotJava cannot be used with Sun WebServer 2.1. This is incorrect. It should state that both HotJava and Netscape can be used with Sun WebServer 2.1. When HotJava is used, it must be version 1.1.4 or later.

Sun WebServer2.1 Cannot Be Chosen As Web Server for Solaris Web Start

The Product Compatibility table in Appendix B states that Sun WebServer 2.1 can optionally be chosen to be the web server for Solaris Web Start. This is incorrect. It should say: "N/A".

HotJava Versions Supported by the SMC

The Product Compatibility table in Appendix B states that the Solaris Management Console requires HotJava 1.0.3 or 1.1.3. If the SMC has not been updated, then HotJava version 1.0.1 should be used.

SolsticeTM Internet Mail Server 2.0 Installation and Configuration Guide

On page 17, in printed versions of the Solstice Internet Mail 2.0 Installation and Configuration Guide, the internet service name on /etc/service and /etc/inetd.conf should be pop3 instead of pop-3.

Solaris PC NetLink 1.1 Release Notes

The release note for "Configuring a WINS Server as a WINS Client" suggests using the command winsadm --p ipaddress as the workaround. This is incorrect. The correct command to use as workaround is winsconf --p ipaddress.

SMC Online Help

Book Affected: Solaris Management Console online help

In the section "Solaris Management Console Overview," under "To View the Server Audit Log," it incorrectly refers to the audit log file as /usr/adm/messages. The correct audit log file is /var/adm/messages.

In the client installation section, it says:"

 # cd /cdrom/cdrom0/products/Solaris_Management_Console_1.0/Solaris_2.6
."

It should say: "

# cd /cdrom/cdrom0/products/Solaris_Management_Console_1.0
."

Book Affected: Solaris Management Console online help

In the section titled "Solaris Management Console Troubleshooting," is a topic titled "SMC Server: No Applications Shown." Within that topic is a statement that says:You can use the jar -cf command to get a listing of the contents of the jar file in question.

The proper command is jar -tf /usr/sadm/smc/beans/SMC.jar. If you use the jar -cf command, you will destroy the backup file (SMC.jar.bak).