|
|
|
CA Server Automation is an internationalized product (i18n) that uses UTF-8 character encoding to display language-specific characters. For example, the German ü (umlaut), the French è (grave accent), or Japanese characters in input and output data are displayed.
The UTF-8-encoded character support includes, but is not limited to, the following areas:
The installation of this product is supported on English, French, German, and Japanese versions of the supported Microsoft Windows operating systems. Also, for Windows, you can use a supported version of SQL Server that is either English, or the appropriate localized version for that operating system.
Important! If you edit a product file that uses UTF-8 encoding, be sure to save it with UTF-8 encoding. Operating systems that are not English and have multibyte characters must be saved with UTF-8 encoding. Windows Notepad can save with UTF-8 encoding.
General Limitations
Because CA Server Automation integrates with other CA products, review the international support statements for integration products.
CA Server Automation supports only host or cluster names with the characters 'a - z', 'A - Z', '0 - 9' and '-'. A host or cluster name cannot start with a hyphen ('-') or be all numeric. The NetBIOS name of a Windows system must match its DNS host name. CA Server Automation supports non-ASCII Virtual Machine names, but only if they are provisioned using the virtualization vendor software directly. When cloning or provisioning a new Virtual Machine from within CA Server Automation, the Virtual Machine name must be ASCII.
CA Server Automation supports only ASCII characters in:
Customize Console Display
If you want to display console data that contains language-specific characters, verify the following prerequisites for CLI commands and the NodeCfgUtil utility:
echo $LANG
If UTF-8 is not enabled, enter, for example, the following command in a console window (use the appropriate character encoding: en_US.UTF-8, ja_JP.UTF-8, fr_BE.UTF-8, de_DE.UTF-8, and so on):
LANG=en_US.UTF-8; export LANG
AutoShell and CA Server Automation CLI Commands
AutoShell and CA Server Automation CLI commands support the -locale switch that allows you to specify a locale based on an IS0 639_3166 combination (for example: fr_FR for French). See the Invoking AutoShell section and CLI Commands in the Reference Guide.
Solaris Zones Uptime
The Solaris Zone Uptime MIB attribute (zoneAimStatZoneUpTime) is specified as DisplayString that supports ASCII characters only. The corresponding fields in the user interface do not display UTF-8 characters.
Default Package Wrapper Name
The default package wrapper name is not localized and reads 'default' in all supported languages. Custom package wrapper names support UTF-8 characters.
Service Response Monitoring AIM Configuration File
When you modify the svcrsp.cf configuration file to add language-specific characters, verify that the text editor you use supports UTF-8 as a storage format. If your text editor inserts a UTF-8 Byte Order Mark when saving the file, SystemEDGE ignores the Byte Order Mark when reading the configuration file.
Service Response Monitoring CLI Commands
The svcwatch CLI supports localized output and console help information.
If you use the optional –L switch, the utility detects the current locale of the console and language catalog if available. If a language catalog is not found, the utility falls back to English as a default language.
Cisco UCS Limitations
The Cisco Unified Computing System (Cisco UCS) only supports English language characters. Because the UCS Manager treats non-English characters as invalid, CA Server Automation disallows unsupported characters in UCS fields for service profile, pools, and so on.
Rapid Server Imaging Limitations
The RSI Server does accept localized strings (utf-8) for names and descriptions of images, driver sets and driver collections, and stores them in its database. However, it runs only on an English server and does not display localized messages. The RSI agents are also supported only on English servers and so capture/deploy of non-English servers are not supported. The Server Automation integration with the RSI server also accepts utf-8 strings for names and descriptions of images, driver sets and driver collections. CA Server Automation has its own localized messages that are displayed, however, the English-only messages from the RSI server is passed through as is.
CA Configuration Automation Limitations
CA Configuration Automation supports only ENG SQL server.
Reservation Manager Requirement for a Common Windows Administrator Account Name
The Reservation Manager requires that all Windows systems that are provisioned, to have a common administrator account name. Because the default administrator account name can differ based on the language of the Windows OS, consider creating a common account name on all systems.
Reservation Manager Limitations
The names of virtual machines deployed by the Reservation Manager contain only these characters: 'a - z', 'A - Z', '0 - 9' and '-'. This limitation is enforced to restrict the host names for virtual machines to characters supported by the product.
Business Objects Reports
Business Object reports require Microsoft SQL Server, English, or Japanese versions; no other languages are supported.
Installation Limitations
You can specify the language for a silent installation by using the parameter, –L <locale> (for example, Install.exe –L fr). The following locales are supported: en (English), ja (Japanese), de (German), and fr (French). If you do not specify a locale, the installer chooses the best fit (system locale or English (en)).
The DVD install path that you specify cannot contain Chinese characters, unless it is a Chinese system. If you specify Chinese characters on a non-Chinese system, the installer fails with the following message:
Unable to extract the compressed file. Please get another copy of the installer and try again.
The product installer accepts non-ASCII characters for the configuration of LPAR, vCenter, Solaris Zones, Microsoft Cluster Service, Hyper-V, SCVMM, Remote Monitoring, and UCS components. However, if non-ASCII characters are entered, the configuration of the associated AIMs can silently fail. If you have to configure an AIM using non-ASCII characters, then configure the AIM post-install using the UI Administration tab or CLI.
| Copyright © 2013 CA. All rights reserved. |
|