Problem Note 14227: Using the Object Spawner in a clustered environment
A clustered environment can be described as a group of independent
computer systems, known as nodes or hosts, that work together as a
single system to ensure that mission-critical applications and resources
remain available to clients.
In order for the Object Spawner to run in a clustered environment, the
Object Spawner has to access a given host name instead of performing a
TCP hostname() lookup. A cluster has a logical name (DNS alias) that
can be used for all nodes instead of each nodes individual hostname.
In order for the Object Spawner to recognize the DNS alias that is
associated with the cluster, the Object Spawner must be started with the
-dnsMatch option.
For example, SAS servers and Object Spawners are installed on two
different machines (machine1.my.com and machine2.my.com). The DNS alias
(server1.my.com) resolves to both of these machines. If the client
sends a request to the alias (server1.my.com in this example), one of
the two Object Spawners will receive it.
In this example, the Object Spawner would be started with -dnsMatch
option and look something similar to the following:
UNIX> !sasroot/utilities/bin/objspawn -configfile /tmp/objspawn.cfg
-dnsMatch server1.my.com
For more information on using the -dnsMatch option as a parameter on the
Object Spawner, reference the SAS Integration Technologies : Server
Administrator's Guide: Spawner Invocation Options.
A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:
http://www.sas.com/techsup/download/hotfix/e9_sbcs_prod_list.html#014227
For customers running SAS with Asian Language Support (DBCS), this
fix should be downloaded from:
http://www.sas.com/techsup/download/hotfix/e9_dbcs_prod_list.html#014227
Operating System and Release Information
SAS System | SAS Integration Technologies | Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M3 | 9.1 TS1M3 SP2 |
Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M3 | 9.1 TS1M3 SP2 |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.1 TS1M3 | 9.1 TS1M3 SP2 |
Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M3 | 9.1 TS1M3 SP2 |
Microsoft Windows 2000 Server | 9.1 TS1M3 | 9.1 TS1M3 SP2 |
Microsoft Windows 2000 Professional | 9.1 TS1M3 | 9.1 TS1M3 SP2 |
Microsoft Windows 2000 Advanced Server | 9.1 TS1M3 | 9.1 TS1M3 SP2 |
Microsoft Windows 2000 Datacenter Server | 9.1 TS1M3 | 9.1 TS1M3 SP2 |
OpenVMS Alpha | 9.1 TS1M3 | 9.1 TS1M3 SP2 |
z/OS | 9.1 TS1M3 | 9.1 TS1M3 SP2 |
Microsoft Windows NT Workstation | 9.1 TS1M3 | 9.1 TS1M3 SP2 |
64-bit Enabled HP-UX | 9.1 TS1M3 | 9.1 TS1M3 SP2 |
HP-UX IPF | 9.1 TS1M3 | 9.1 TS1M3 SP2 |
Linux on Itanium | 9.1 TS1M3 | 9.1 TS1M3 SP2 |
Microsoft Windows XP Professional | 9.1 TS1M3 | 9.1 TS1M3 SP2 |
64-bit Enabled Solaris | 9.1 TS1M3 | 9.1 TS1M3 SP2 |
Linux | 9.1 TS1M3 | 9.1 TS1M3 SP2 |
64-bit Enabled AIX | 9.1 TS1M3 | 9.1 TS1M3 SP2 |
Tru64 UNIX | 9.1 TS1M3 | 9.1 TS1M3 SP2 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | medium |
Topic: | Software Components ==> Object Spawner
|
Date Modified: | 2005-04-08 15:22:19 |
Date Created: | 2005-01-18 09:09:48 |