This section lists the known documentation issues for the 4.60 release.
The published documentation incorrectly states that the default
printer driver used when printing from a Microsoft Windows
application server to a client printer attached to a UNIX,
Linux, or Mac OS X client device is QMS 1060 Print
System
.
The default printer driver is HP Color LaserJet 2800
Series PS
.
On page 243 of the
Oracle Secure Global Desktop 4.6 Administration Guide, the
information about the
default.printerinfo.txt
configuration file
should read as follows:
When SGD is first installed, the
default.printerinfo.txt
file contains the
following entry:
[UNIX] "_Default" = "HP Color LaserJet 2800 Series PS" PostScript
With this configuration, when users print from a Windows
application server, they see a printer called
_Default
. This printer prints to the default
printer on the client using a basic PostScript printer driver,
"HP Color LaserJet 2800 Series PS".
The released documentation does not include full details for the Span Multiple Monitors (Kiosk Mode) client profile setting.
On page 193 of the Oracle Secure Global Desktop 4.6 Administration Guide, add the following note to the section on “Configuring Desktop Size for Kiosk Mode Applications”.
The desktop size for kiosk mode applications can also be configured from the webtop. Use the Span Multiple Monitors (Kiosk Mode) option in the Client Settings tab.
On page 317 of the Oracle Secure Global Desktop 4.6 Administration Guide and page 43 of the Oracle Secure Global Desktop 4.6 User Guide, add the following entry to the table of client profile settings.
Setting | Description |
---|---|
Span Multiple Monitors (Kiosk Mode) | Enables X applications to be displayed in kiosk mode on a multihead or dual head monitor. When enabled, the kiosk mode display is spanned across all monitors. When disabled, the kiosk mode display is displayed using the primary monitor only. This is the default setting. |
In the “Using Multihead or Dual Head Monitors” section on page 193 of the Oracle Secure Global Desktop 4.6 Administration Guide, replace the following paragraphs in the “Configuring Desktop Size for Kiosk Mode Applications” section.
“X applications can be displayed in kiosk mode on a multihead or dual head monitor.
You configure kiosk mode display features with the
<KioskArea>
entry in the
<localsettings>
section of the client
profile, profile.xml
on the client device. If
the <localsettings>
section is not present
in the client profile, create a new section.
The <KioskArea>
entry defines the screen
area used by kiosk mode. The available values are as follows:
virtual – Uses the virtual screen size. All monitors are used.
0
– Uses the primary monitor only.
This is the default value.
1
– Uses the secondary monitor
only.
n – (Multihead monitors only). Uses the nth secondary monitor only.
For example, to span the kiosk mode display across all monitors:”
<KioskArea>virtual</KioskArea>
The following paragraph in the “Recovery Stage” section on page 340 of the Oracle Secure Global Desktop 4.6 Administration Guide is incorrect.
“If an array splits into more than two arrays during the failover stage, the original array formation cannot be recreated automatically. Manual recovery must be used.”
The paragraph should read as follows:
“If an array splits into more than two arrays during the
failover stage and the Action When Failover Ends
(--array-primaryreturnaction
)
attribute is configured as Restore original primary
(accept
), the original array
formation is recreated automatically.
If the Action When Failover Ends attribute is configured as
Restore array with a new primary
(acceptsecondary
), the
original array formation cannot be recreated automatically.
Manual recovery must be used.”
On page 170 of the
Oracle Secure Global Desktop 4.6 Administration Guide, the path to
the sgd-webservices.jar
file is incorrect.
The correct path is as follows:
/opt/tarantella/bin/java/com/sco/tta/soap/services/proxy
.
The released documentation contains inaccurate information about editing a list of attributes from the command line.
In the Oracle Secure Global Desktop 4.6 Gateway Administration Guide:
On page 59, the paragraph should read as follows:
“Separate multiple
filter-spec
entries with a comma,
and enclose the entire string in double quotation marks
(""
).”
On page 60, the example for configuring multiple connection filters should read as follows:
"192.168.0.250:sgdg:gateway1.example.com:443,\ *:direct:sgd1.example.com:80"
In the Oracle Secure Global Desktop 4.6 Administration Guide:
On page 5, the example of external DNS names configuration should read as follows:
$ tarantella config edit --server-dns-external \ "192.168.10.*:boston.example.com" "*:www.example.com"
On page 12, the example of array routes configuration should read as follows:
"192.168.5.*:CTDIRECT" \ "192.168.10.*:CTSOCKS:taurus.example.com:8080" \ "*:CTSOCKS:draco.example.com:8080:ssl"
On page 13, the paragraph describing how to configure multiple filters in an array route should read as follows:
“Separate each filter with a space and enclose in
double quotation marks (""
). For example,
"filter1" "filter2" "filter3"
.”
On page 391 in the Log Filters section, the paragraph should read as follows:
“Separate multiple filter
entries with a space and enclose each filter in double
quotation marks (""
).”
On page 496 in the External DNS Names section, the sentence at the end of the Usage paragraph should read as follows:
“Separate multiple DNS names with a space and enclose
each DNS name in double quotation marks
(""
) .”
On the same page, the example of external DNS names configuration should read as follows:
--server-dns-external "192.168.10.*:boston.indigo-insurance.com" "*:www.indigo-insurance.com"
Following the closure of the Sun documentation site
(docs.sun.com
), the released documentation
may contain incorrect documentation URL and customer feedback
email address details.
The documentation URL should read as follows:
http://docs.oracle.com/cd/E19351-01/index.html
The published email address for customer comments is no longer available.
This change affects the following documentation:
Oracle Secure Global Desktop 4.6 Administration Guide
Oracle Secure Global Desktop 4.6 Installation Guide
Oracle Secure Global Desktop 4.6 User Guide
Oracle Secure Global Desktop 4.6 Gateway Administration Guide
Oracle Secure Global Desktop 4.6 Platform Support and Release Notes
Appendix D of the
Oracle Secure Global Desktop 4.6 Administration Guide incorrectly
lists the --force
option for the
tarantella stop and tarantella
restart commands.
The --force
option was deprecated in the 4.6
release and is no longer available.
The table of command options for the SGD Remote Desktop Client
on page 152 of the
Oracle Secure Global Desktop 4.6 Administration Guide incorrectly
states that the default setting for the
-windowskey
option is
on
.
The default setting for the
-windowskey
option is
off
.
The following applications troubleshooting topic is missing from the released documentation.
Application startup can take longer than expected if SGD attempts to use an X display port that is being used by another service. Application startup eventually completes successfully.
The solution is to exclude the port from use by the X Protocol Engine.
In the Administration Console, go to the Protocol Engines, X tab
for each SGD server in the array and type
-xport
portnum
in
the Command-Line Arguments field, where
portnum
is the TCP port number to
exclude.
Alternatively, use the following command:
$ tarantella config edit --xpe-args "-xport portnum
"
To exclude several ports, you can specify
-xport
portnum
multiple times, as follows:
$ tarantella config edit \ --xpe-args "-xportportnum_1
" "-xportportnum_2
" "-xportportnum_3
"
The changes made take effect for new X Protocol Engines only. Existing X Protocol Engines are not affected.
The --suffix-mappings
option
for the tarantella service command is
incorrectly documented.
In the tables of command options on page 820 and page 825 in Appendix D of the Oracle Secure Global Desktop 4.6 Administration Guide, the following paragraph is incorrect:
“Applies only to Active Directory service objects.”
This paragraph should read as follows:
“Applies to Active Directory service objects and LDAP service objects that connect to Active Directory.”
The initial sentence in the “Suffix Mappings” section on page 98 in Chapter 2 of the Oracle Secure Global Desktop 4.6 Administration Guide, should read as follows:
“The following information applies to Active Directory service objects and LDAP service objects that connect to Active Directory.”
In this release, the Window Manager
(--winmgr
) attribute is not
available when you create a new Windows application object using
the tarantella object new_windowsapp command.
The documentation for the tarantella object
new_windowsapp command on page 744 in Appendix D of
the Oracle Secure Global Desktop 4.6 Administration Guide
incorrectly lists the
--winmgr
attribute.
Details for the tarantella config reload command are missing from the released documentation.
The following information should be included in the “The tarantella config Command” section on page 688 in Appendix D of the Oracle Secure Global Desktop 4.6 Administration Guide.
Reloads properties for the server where the command is run.
tarantella config reload [ --login-beans ]
The following table shows the available options for this command.
Option | Description |
---|---|
|
Reloads server properties related to authentication,
such as
This option can be used to reload properties on a secondary server, without restarting the server. |
The following example reloads all authentication properties for the server where the command is run.
$ tarantella config reload --login-beans
The documentation for the Windows Audio Sound Quality
(--array-audio-quality
)
attribute on page 468 in Appendix A of the
Oracle Secure Global Desktop 4.6 Administration Guide is incorrect.
The description of the High Quality Audio setting should read as follows:
High Quality Audio – 44.1 kHz.
The following paragraph is missing from the Description section on the same page:
“If the application server hosting the Windows application does not support the High Quality Audio setting, the audio rate is downgraded automatically.”
The following sentence in the “Upgrading the SGD Gateway” section on page 5 of the Oracle Secure Global Desktop 4.6 Gateway Administration Guide is incorrect.
“When you upgrade the SGD Gateway, your original configuration, such as keystores and routing proxy configuration files are preserved. There is no need to reconfigure the SGD Gateway after upgrading.”
This sentence should read as follows:
“When you upgrade the SGD Gateway, most of your original configuration, such as routing proxy configuration files is preserved. However, the upgrade process overwrites any self-signed certificates used by the Gateway.
After an upgrade, you must reconfigure the SGD Gateway. Follow the standard configuration steps for authorizing a Gateway to SGD, as described in “How to Install SGD Gateway Certificates on the SGD Array” on page 16.”
See Section 3.1.17, “6963320 – Cannot Connect to SGD Using Version 4.5 of the SGD Gateway, or Using an Upgraded Version 4.6 Gateway” for more details about reconfiguring the SGD Gateway following an upgrade.
The following sentence is missing from the “For PDF Printing, is Ghostscript Available on the SGD Host?” printing troubleshooting topic on page 250 in Chapter 5 of the Oracle Secure Global Desktop 4.6 Administration Guide.
“Try upgrading to the latest version of Ghostscript. After
upgrading, ensure that the symbolic link
/opt/tarantella/var/info/gsbindir
points to
the directory where the new Ghostscript binaries are
installed.”