Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices
This section provides the product requirements for the Sun Ray Software 5.3 release.
Table 3.1, “Supported Sun Ray Software Operating Systems” lists the supported Sun Ray Software operating systems for the Sun Ray Software 5.3 release.
Table 3.1. Supported Sun Ray Software Operating Systems
Operating System | Supported Releases |
|---|---|
Oracle Solaris on SPARC and x86 platforms |
Note: Oracle Solaris 11 is not supported. |
Oracle Linux on x86 platform (32-bit and 64-bit) |
|
Oracle products certified on Oracle Linux are also certified and supported on Red Hat Enterprise Linux due to implicit compatibility between both distributions. Oracle does not run any additional testing on Red Hat Enterprise Linux products.
For additional operating system requirements, see Section 3.1.7, “Additional Oracle Linux Requirements” and Section 3.1.6, “Additional Oracle Solaris Requirements”.
The Sun Ray Operating Software 11.0 for Sun Ray Clients is required for many of the new Sun Ray Software 5.3 features. Sun Ray Operating Software is the official name of the Sun Ray Client firmware.
See Section 3.2.4, “Installing Firmware Before Sun Ray Software Installation” for details on how to install the Sun Ray Operating Software on Sun Ray Clients.
The following Windows remote desktops are supported with Sun Ray Software:
Windows XP Professional with SP2 (64-bit)
Windows XP Professional with SP3 (32-bit)
Windows Server 2003 R2 SP2 Enterprise Edition (32-bit and 64-bit)
Windows 7 SP1 Enterprise Edition (32-bit and 64-bit)
Windows Server 2008 R2 SP1 Enterprise Edition (64-bit)
Table 3.2, “Supported Features for Windows Remote Desktops” shows what features are supported for each Windows remote desktop. Some Windows releases require a Windows connector component to be installed for specific feature support. For detailed information, see Section 3.2.6, “How to Install the Windows Connector Components on a Windows System”.
Table 3.2. Supported Features for Windows Remote Desktops
Windows XP SP2 (64-bit) | Windows XP SP3 (32-bit) | Windows Server 2003 R2 SP2 (32-bit/64-bit) | Windows 7 SP1 (32-bit/64-bit) | Windows Server 2008 R2 SP1 (64-bit) | |
|---|---|---|---|---|---|
Video Acceleration | x | x | x | x | x |
USB Redirection | x | x | x | x | x |
Audio Input | x | x | x | x | x |
Enhanced Network Security (TLS/SSL and NLA) | x | x | x | x | x |
Session Directory/Session Broker | N/A | N/A | x | N/A | x |
The following Sun Ray Software features are not supported on a Sun Ray server running the Oracle Linux platform.
Smart card services, including PIN login, email signing, and other smart card related operations, are not supported.
Using mass storage devices without the USB redirection Windows component provides much lower performance on Oracle Linux than Oracle Solaris due to the design of the Oracle Linux mass storage subsystem. Use USB redirection for optimum performance with mass storage devices.
Predefined kiosk session types are not available, which provide a desktop, a window manager, and the ability to configure a set of applications. Sun Java Desktop (JDS), Release 3, is an example of a predefined session type provided for Oracle Solaris. See Section 10.1, “Kiosk Overview” for more information.
The CCID IFD handler, which provides access to external USB smart card readers connected to Sun Ray Clients, is not supported on Sun Ray servers running Oracle Linux.
Table 3.3, “Disk Space Requirements” lists the disk space requirements for specific directories.
Table 3.3. Disk Space Requirements
Default Installation Path | Requirements |
|---|---|
| 1 Mbyte |
| 0.1 Mbytes |
| 70 Mbytes |
| 4.6 Mbytes |
| 5 Mbytes |
| 2.5 Mbytes |
| Allow enough disk space for the data store and log files. For 1,000 entries, allocate roughly 1.5 Mbytes of disk space, 64 Mbytes of RAM, and 128 Mbytes of swap space. |
| 5 Mbytes |
When using Oracle Solaris for a Sun Ray server, the following requirements must be met:
The Entire Distribution software cluster is required and must be installed.
The latest Recommended Patchset must be installed prior to the Sun Ray Software installation, which you can download from My Oracle Support.
The Common Desktop Environment (CDE) might not be available in a future Oracle Solaris release. Users should migrate to the Java Desktop System. CDE will not be supported on future versions of Sun Ray Software when CDE is officially removed from the Oracle Solaris release.
Oracle Solaris 10 uses zones to permit multiple virtualized operating system environments to coexist in a single instance of Oracle Solaris, allowing processes to run in isolation from other activity on the system for added security and control. Sun Ray Software releases are supported only in the global zone.
The default Oracle Linux RPMs are required for Sun Ray Software and must be installed on the Sun Ray server. There are also a number of additional RPMs that are required, which you can install using the utpkgcheck command provided in the Sun Ray Software media pack.
The utpkgcheck command requires the server to be registered with Unbreakable Linux Network (ULN) or the Oracle Linux DVD to be mounted on the server. The ULN yum repository is checked first. For details on how to register a system with ULN, see http://linux.oracle.com/uln_faq.html .
Use the following command to display the missing RPMs on the Oracle Linux server:
# utpkgcheck
Use the following command to install the required RPMs on the Oracle Linux server:
# utpkgcheck -i
The Firewall and SELinux services must be disabled during the post-installation setup.
Sun Ray Software 5.3 requires a 32-bit implementation of a Java(TM) 2 Platform, Standard Edition JRE(TM) of at least 1.6. The latest Java release is available at http://www.oracle.com/technetwork/java/javase/downloads.
To check what JRE version is installed on your system, use the following command:
# java -version
A supported version of JRE is also bundled in the unzipped Sun
Ray Software media pack for Oracle Solaris and Oracle Linux systems in the
Supplemental directory.
A 64-bit JRE is not suitable for use with Sun Ray Software. The 32-bit JRE is required, even when the platform is capable of supporting a 64-bit JRE.
The Sun Ray Software installation script assumes JRE is
installed in the /usr/java directory by
default. If you want to accept the default when installing the
Sun Ray Software on an Oracle Linux server, install JRE 1.6 or later
on the server and then create a symlink from
/usr/java to the newly created
jre directory. For example, the following
command creates a symbolic link from the
/usr/java directory to the
jrel.6.0_23 directory located in
/usr.
# ln -s jre1.6.0_23 /usr/java
The Sun Ray Administration Tool (Admin GUI) requires that a Web server be installed and running on each Sun Ray server. The Admin GUI must be hosted in a web container that supports the JavaServlet 2.4 and JavaServer Pages 2.0 specification. The Apache Tomcat 5.5 Web container implements these standards and runs on any operating system that has a Java Runtime Environment (JRE).
The utconfig script prompts for the location of an Apache Tomcat HTTP Server and asks whether it should be configured automatically.
To configure the server automatically, supply the path and answer Yes.
To configure the HTTP server later by using the utconfig -w command, answer No.
An Apache Tomcat 5.5 archive is included in the Sun Ray Software
media pack under
Supplemental/Apache_Tomcat. The most recent
version of Tomcat 5.5 can be downloaded from
http://tomcat.apache.org.
The Sun Ray configuration script uses port 1660 for the Sun Ray Administration Tool (Admin GUI) by default. If this port is unavailable, you can configure a new port while running the utconfig command.
See How to Install Apache Tomcat for details.
Table 3.4, “Web Browser Requirements” lists the tested and supported browsers for the Sun Ray Administration Tool (Admin GUI).
Table 3.4. Web Browser Requirements
Operating System | Browser Support |
|---|---|
Oracle Solaris 10 9/10 or later | Firefox 3.6.16 |
Oracle Solaris 10 9/10 or later with Trusted Extensions | Firefox 3.6.16 |
Oracle Linux 5.6 | Firefox 3.6.13 |
Oracle Linux 5.7 | Firefox 3.6.18 |
When you configure a new Sun Ray server in a failover environment that uses Sun Ray Software 5.3 only, service port 7012 is used by default.
If you already have an LDAP (Lightweight Data Access Protocol) server configured on the Sun Ray server, it can coexist with the Sun Ray data store. However, it must not use port 7012, which is reserved for use by the Sun Ray data store.
If you configure a new Sun Ray server in a failover group with mixed versions of Sun Ray Software, you must make sure that the primary server is running Sun Ray Software 5.3.
If the secondary server is running Sun Ray Software 5.3, no special care is required. The utreplica utility automatically synchronizes with the port number on the primary.
Although configuring mixed failover groups consisting of servers running various versions of Sun Ray Server Software is possible, this practice is discouraged. For more information, see Chapter 6, Failover Groups.
If Tomcat 5.5 is already installed on your system, you can omit the steps below and specify the path, if necessary, during the Sun Ray Software configuration.
As superuser, open a shell window on the Sun Ray server.
% su -
Change to the Apache_Tomcat directory.
For example:
# cd <media_pack_directory>/Supplemental/Apache_Tomcat
Extract the Tomcat archive into a suitable directory, such
as /opt.
For Oracle Solaris
The Tomcat archive uses GNU tar extensions and must be untarred with a GNU-compatible version of the tar command, such as gtar.
# /usr/sfw/bin/gtar -xvz -C /opt -f apache-tomcat-5.5.20.tar.gz
For Oracle Linux
# tar -xvz -C /opt -f apache-tomcat-5.5.20.tar.gz
(Optional) Create a symbolic link to the default location for the Sun Ray Software installation script.
# ln -s apache-tomcat-5.5.20 /opt/apache-tomcat
The following section summarize Sun Ray system port and protocol usage.
The range of dynamic/UDP ports on the server is constrained to the range defined by the
utservices-low and utservices-high UDP service
definitions, whose default values in /etc/services are 40000 and 42000
respectively. This range should not be redefined to constrain ports too tightly. The range
of ports must be sufficient to provide several ports per connected Sun Ray Client.
Ranges used by the client include the following:
Dynamic/TCP ports on the client are in the range 32768-65535.
Dynamic/UDP ports on the client are in the range 4096-65535.
ALP rendering traffic (ALP-RENDER) always uses a UDP port number greater than 32767 at the client.
Table 3.5, “Sun Ray Client-to-Server Ports and Protocols” lists the Sun Ray Client-to-server ports and protocols. In the table, a double-headed arrow in the Flow column indicates the direction of the initial packet. In most cases, the client (a Sun Ray Client or Oracle Virtual Desktop Client) initiates the interaction.
Table 3.5. Sun Ray Client-to-Server Ports and Protocols
Client Port / Flow | Protocol | Server Port / Flow | Peer | Importance/Comments |
|---|---|---|---|---|
66/UDP (BOOTPC/DHCPC) broadcast=>> unicast=>> | DHCP | 67/UDP (BOOTPS/DHCPS) <=broadcast <=unicast | DHCP Service | Mandatory Network and configuration parameter discovery |
Dynamic/UDP unicast=>> | TFTP | 69/UDP (TFTP) <=unicast | TFTP Service | Recommended Firmware download (Configuration parameter download) |
Dynamic/UDP unicast=>> | DNS | 53/UDP (domain) <=unicast | DNS Service | Optional For server name lookups |
514/UDP (syslog) unicast=>> | Syslog | 514/UDP (syslog) | Syslog Service | Optional Event reporting |
Dynamic/UDP broadcast=>> | ALP-DISCOVERY | 7009/UDP (utauthd-gm) <=unicast | Sun Ray Server | Optional On-subnet Sun Ray server discovery |
Dynamic/TCP unicast=>> | ALP-AUTH | 7009/TCP (utauthd) <=unicast | Sun Ray Server | Mandatory Presence, control, status |
Dynamic/UDP with port number >= 32768 unicast=> or unicast=>> when NAT is in use | ALP-RENDER | Dynamic/UDP constrained by utservices-low and utservices-high <<=unicast or <=unicast when NAT is in use | Sun Ray Server | Mandatory On-screen drawing, user input, audio |
5498/UDP unicast=>> | ALP-AUDIO-IN | Dynamic/UDP constrained by utservices-low and utservices-high | Sun Ray Server | Optional Inbound audio |
Dynamic/TCP unicast=>> | ALP-DEVMGR | 7011/TCP (utdevmgr) <=unicast | Sun Ray Server | Optional Device management |
7777/TCP unicast=> | ALP-DEVDATA | Dynamic/TCP <<=unicast | Sun Ray Server | Optional Device data transfer |
7013/UDP (utquery) unicast=> | ALP-QUERY | Dynamic/UDP <<=unicast <<=broadcast | Any | Optional utquery support |
Due to CR 12301209, the keyboard may become unresponsive to input. To work around this issue, allow ICMP messages to flow from the Sun Ray server to the client.
Table 3.6, “Sun Ray Server-to-Server Ports” lists the Sun Ray server-to-server ports.
Table 3.6. Sun Ray Server-to-Server Ports
Sun Ray Server Port | Protocol | Port | Peer | Notes |
|---|---|---|---|---|
<<=ARP=>> | All on subnet | IP-to-MAC mapping | ||
Transient | SYSLOG/UDP unicast=>> | 514 (SYSLOG) | Syslog Server | Status reporting, if required |
7009 (UTAUTHD) | <<=UTAUTHD-GM/UDP=>> broadcast or multicast | 7009 (UTAUTHD) | Sun Ray Server | Group discovery, if required |
7011 (UTDEVMGRD) | <<=UTDEVMGRD/TCP=>> | 7011 (UTDEVMGR) | SR Group Member | Device control and status |
7008 (UTRCMD) | <<=UTRCMD/TCP=> | Privileged | SR Group Member | Remote execution |
<<=ICMP ECHO=> | Any | Admin: presence | ||
7010 (UTAUTH-CB) | <<=UTAUTH-CB/TCP=> | Transient | Any | Admin: control and status |
7012 (UTDS) | <<=UTDS/TCP=> | Transient | Any | Data store, if required. |
7007 (UTSESSIOND) | <<=UTSESSION/TCP=> | Transient | Any | Session members |
7011 (UTDEVMGR) | <<=UTDEVMGR/TCP=> | Transient | Any | Device clients |
1660 (HTTP) | <<=HTTP/TCP=> | Transient | Localhost | Web GUI, if configured |
1661 (HTTPS) | <<=HTTPS/TCP=> | Transient | Localhost | Web GUI, if configured |
7007 (UTSESSIOND) | <<=UTSESSION/TCP=> | Privileged | Localhost | Session management |
For basic Windows connector operations (RDP port access), the Windows server firewall needs TCP port 3389 open for inbound connections. The Sun Ray server (where the Windows connector is running) firewall needs TCP port 3389 open for outbound connections.
For multimedia redirection, the Windows server firewall must have a TCP port between 6000 and 10000 open for inbound connections. The Sun Ray server (where the Windows connector is running) firewall must have a TCP port between 6000 and 10000 open for outbound connections.
Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices