Post on 04-Jun-2018
transcript
Installation Notes
BMC BladeLogic Client AutomationVersion: 8.2.01May 18, 2012Supported platforms and system requirements
BMC Software has released version 8.2.01 of the BMC BladeLogic Client Automation product. This document provides information about supported platforms and system requirements for the product. This information supplements and supersedes information in the product documents.
Supported operating systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Footprint of the tuner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Platform requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Requirements for packaging software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Requirements for packaging content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Requirements for transmitters and proxies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Requirements for the CMS console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Requirements for Patch Management source channels . . . . . . . . . . . . . . . . . . . . . . 14Requirements for endpoints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Database platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Support for Directory Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Support for embedded Software Development Kits (SDKs) platforms. . . . . . . . . . . . 23Support for browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Support for languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Support for Java Virtual Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Support for Directory Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
NOTE Details about recent patches for this product are available from the BMC Software Customer Support website at http://www.bmc.com/support_home. Before installation, BMC Software recommends that you check the website to determine whether patches or zaps are available for this product.
*260808**260808*
*260808*
Supported operating systems
Supported operating systemsTable 1 identifies the operating systems that are supported by BMC BladeLogic Client Automation 8.2.01.
Table 1 Platforms supported by in version 8.2.01 (part 1 of 2)
Platform Description Notes Support Added
Linux®■ Red Hat Enterprise Linux (RHEL)
Server/Client 5.x (Latest Supported 5.8)(32-bit Tuner)
■ Red Hat Enterprise Linux (RHEL) Server/Client 6.x (Latest Supported 6.2)(32-bit Tuner)
To run 32-bit tuners on a 64-bit Red Hat OS, you must install the Red Hat 32-bit compatibility libraries.
Intel and AMD processors only in 32-bit support.
8.2.01
■ SUSE Linux 11.1 Enterprise Server x64 (32-bit Tuner)
Intel and AMD processors only in 32-bit support. PPC and Itanium are not supported.
The Patch Service is not supported on this platform.
8.2.01
Mac OS X ■ Mac OSX X86 10.x (Latest Supported 10.7)(32-bit Tuner)
■ The Patch Service is not supported on these platforms.
■ SSL is not supported on these platforms.
■ Only endpoints are supported on these platforms.
8.2.01
Microsoft Windows
Windows XP Professional (Latest Supported SP2)(32-bit Tuner)
7.0.00
Windows Vista Enterprise (Latest Supported SP2)(32-bit Tuner)
8.0.00
Windows 7 Professional/Ultimate/Enterprise (Latest Supported SP1)(32-bit Tuner)
8.1.01
Windows Server 2003 x64 (Latest Supported SP2)(32-bit Tuner)
8.0.00
Windows Server 2003 x64 R2 (Latest Supported SP2)(32-bit Tuner)
8.0.00
Windows Server 2008 x64 (Latest Supported SP2)(32-bit Tuner)
8.0.00
Windows Server 2008 x64 R2 (Latest Supported SP1)(32-bit Tuner)
8.0.00
2 Installation Notes May 18, 2012
Footprint of the tuner
Footprint of the tuner A tuner is the interface through which BMC BladeLogic Client Automation components communicate. Operations, including product updates, are carried out through tuner connections. Every machine that runs BMC BladeLogic Client Automation modules must have a tuner installed.
Table 2 provides information about the footprint of the tuner and endpoint service channels. For information about the total disk space and memory requirements for the tuner and the other BMC BladeLogic Client Automation components on a particular machine type, see “Platform requirements.”
The tuner and channels also produce log files, but you can configure the amount of disk space these files use.
VMwarea ESX
GSX
Workstationa VMWare is supported for the infrastructure, console, and endpoints. VMWare is also supported for images
running on top of the ESX server, but not for management of the ESX server. Shared resources on a VM can impact performance in a virtualized environment.
Table 2 Tuner footprint and service channels
Operating systemSize of installer file
Disk space for installed tuner
Temp directory disk space
Workspace with service channelsa
a Service channels include: Scanner Service, Logging Service, Policy Service, Infrastructure Service, Deployment Service, and Patch Service.
Virtual Memory for the Tunerb
b The memory measurement corresponds to the amount of memory required to run only the tuner on an endpoint, and it does not include the memory required for downloading packages, running an inventory scan, or other similar actions.
Linux 174 MB 169.3 MB 175.1 MB 44.6 MB 130.93 MB
Mac OS X 86 110 MB 157.7 MB 115.5 MB 68.8 MB 59.8 MB
Windows 101 MB 190 MB 237 MB 53 MB 137 MB
Table 1 Platforms supported by in version 8.2.01 (part 2 of 2)
Platform Description Notes Support Added
Version 8.2.01 3
Platform requirements
Platform requirementsPlatform requirements differ, depending on how you plan to use a machine. For example, the requirements for a machine that packages applications are different than those of a machine that hosts a transmitter. Platform requirements are organized into the following sections:
■ “Requirements for packaging software” on page 4■ “Requirements for packaging content” on page 7■ “Requirements for transmitters and proxies” on page 9■ “Requirements for the CMS console” on page 12■ “Requirements for Patch Management source channels” on page 14■ “Requirements for endpoints” on page 17
For machines that you plan to use for hosting your database or directory service, see the BMC BladeLogic Client Automation Installation Guide.
Requirements for packaging software
You can run the following BMC BladeLogic Client Automation components on the machines used for packaging software:
■ Tuner 8.1.01 or later■ Application Packager 8.1.01 or later■ Channel Copier or Publisher 8.1.01 or later■ Infrastructure Service 8.1.01 or later■ Scanner Service (optional) 8.1.01 or later■ Logging Service (optional) 8.1.01 or later■ Patch Service (optional) 8.1.01 or later
Table 3 identifies the specific versions of the various platforms on which application packaging is supported.
NOTE The following optional channels are supported on all types of machines: latest version of Certificate Manager, Channel Manager, Console Window, Help Channel, and License Installer.
NOTE On UNIX® and Mac OS X platforms, only the File Packager and Custom Packager components of Application Packager are supported.
4 Installation Notes May 18, 2012
Requirements for packaging software
Linux
Table 3 Requirements for packaging software (using Application Packager)
Platform Version Comments
Linux (Red Hat Enterprise)
■ Red Hat Enterprise Linux (RHEL) Server/Client 5.x (Latest Supported 5.8)(32-bit Tuner)
■ Red Hat Enterprise Linux (RHEL) Server/Client 6.x (Latest Supported 6.2)(32-bit Tuner)
Linux SUSE SUSE Linux 11.1 Enterprise Server x64 (32-bit Tuner)
Mac OS X Mac OSX X86 10.x (Latest Supported 10.7)(32-bit Tuner)
Windows XP Professional (32-bit Tuner) ■ Latest Supported SP 3 for 32-bit■ Latest Supported SP 2 for 64-bit
■ Server 2003 x64 (Latest Supported SP2)(32-bit Tuner)
■ Server 2003 x64 R2 (Latest Supported SP2)(32-bit Tuner)
(32-bit Tuner on 64-bit OS): Intel and AMD processors in 32-bit compatible mode, Recommend SP 2
Windows Server 2008 x64 R2 (Latest Supported SP1)(32-bit Tuner)
Windows Server 2008 x64 (Latest Supported SP2)(32-bit Tuner)
Windows Vista Enterprise (Latest Supported SP2)(32-bit Tuner)
Windows 7 Professional/Ultimate/Enterprise (Latest Supported SP1)(32-bit Tuner)
Table 4 Linux—Requirements for packaging software
Requirement Description
CPU Pentium 133 MHz (minimum)
500 MHz or higher (recommended)
Version 8.2.01 5
Requirements for packaging software
For a list of required UNIX X11 libraries, see the BMC BladeLogic Client Automation Installation Guide.
Mac OS X
Windows
RAM 1 GB (minimum)
2 GB or higher (recommended)
Disk space 105–110 MB
plus the size of the applications you plan to package
Table 5 Requirements for packaging software on Mac OS X
Requirement Description
CPU Power PC G4 800 MHz
RAM 1 GB (minimum)
2 GB or higher (recommended)
Table 6 Requirements for packaging software on Windows
Requirement Description
CPU Pentium 133 MHz (minimum)
500 MHz or higher (recommended)
RAM 1 GB (minimum)
2 GB or higher (recommended)
Disk space 70–100 MB
plus the size of the applications you plan to package
Table 4 Linux—Requirements for packaging software (continued)
Requirement Description
6 Installation Notes May 18, 2012
Requirements for packaging content
Requirements for packaging content
You can run the following BMC BladeLogic Client Automation modules on the machines used for packaging content (data files):
■ Tuner 8.1.01 or later■ Application Packager 8.1.01 or later■ Content Replicator 8.1.01 or later■ Deployment Service 7.5.00.008 or later■ Infrastructure Service 8.1.01 or later■ Scanner Service (optional) 8.1.01 or later■ Logging Service (optional) 8.1.01 or later■ Patch Service (optional) 8.1.01 or later
Table 7 identifies the specific versions of the various platforms on which content packaging is supported:
Table 7 Requirements for content-packaging software (using Content Replicator) (part 1 of 2)
Platform Version Comments
Linux (Red Hat Enterprise)
■ Red Hat Enterprise Linux (RHEL) Server/Client 5.x (Latest Supported 5.8)(32-bit Tuner)
■ Red Hat Enterprise Linux (RHEL) Server/Client 6.x (Latest Supported 6.2)(32-bit Tuner)
Mac OSX Mac OSX X86 10.x (Latest Supported 10.7)(32-bit Tuner)
Linux (SUSE) SUSE Linux 11.1 Enterprise Server x64 (32-bit Tuner)
Windows XP Professional (32-bit Tuner) ■ Latest Supported SP 3 for 32-bit■ Latest Supported SP 2 for 64-bit
■ Windows Server 2003 x64 (Latest Supported SP2)(32-bit Tuner)
■ Windows Server 2003 x64 R2 (Latest Supported SP2)(32-bit Tuner)
(32-bit Tuner on 64-bit OS): Intel and AMD processors in 32-bit compatible mode. Recommend SP 2.
Windows Server 2008 x64 (Latest Supported SP2)(32-bit Tuner)
Windows Server 2008 x64 R2 (Latest Supported SP1)(32-bit Tuner)
Version 8.2.01 7
Requirements for packaging content
Linux
For a list of required UNIX X11 libraries, see the BMC BladeLogic Client Automation Installation Guide.
Mac OS X
Windows Vista Enterprise (Latest Supported SP2)(32-bit Tuner)
Windows 7 Professional/Ultimate/Enterprise (Latest Supported SP1)(32-bit Tuner)
Table 8 Requirements for content-packaging software on Linux
Requirement Description
CPU Pentium 133 MHz (minimum)
500 MHz or higher (recommended)
RAM 1 GB (minimum)
2 GB or higher (recommended)
Disk space 105–110 MB
plus the size of the applications you plan to package
Table 9 Requirements for packaging software Mac OS X
Requirement Description
CPU Power PC G4 800 MHz
RAM 1 GB (minimum)
2 GB or higher (recommended)
Table 7 Requirements for content-packaging software (using Content Replicator) (part 2 of 2)
Platform Version Comments
8 Installation Notes May 18, 2012
Requirements for transmitters and proxies
Windows
Requirements for transmitters and proxies
You can run the following modules on the machines used for transmitters (including mirrors and repeaters) and proxies:
■ Tuner 8.1.01 or later■ Transmitter 8.1.01 or later or Proxy Server channel 8.1.01 or later■ Infrastructure Service 8.1.01 or later■ Scanner Service (optional) 8.1.01 or later■ Logging Service (optional) 8.1.01 or later■ Patch Service (optional) 8.1.01 or later■ Transmitter Administrator Command Line or Proxy Administrator Command
Line (optional) 8.1.01 or later■ NT Domain Authenticator (optional transmitter extension) 7.1.00 or later
The following plug-ins can be hosted on transmitters:
■ Policy Service plug-in■ Inventory plug-in■ Logging plug-in■ Infrastructure Service plug-in■ Patch Service plug-in■ Patch Repository plug-in
Table 10 Requirements for content-packaging software on Windows
Requirement Description
CPU Pentium 133 MHz (minimum)
500 MHz or higher (recommended)
RAM 1 GB (minimum)
2 GB or higher (recommended)
Disk space 70–100 MB
plus the size of the applications you plan to package
Version 8.2.01 9
Requirements for transmitters and proxies
Table 11 identifies the specific versions of the various platforms on which transmitters and proxies are supported:
Table 11 Platforms for transmitters or proxies
Platform Version Comments
Linux (Red Hat Enterprise)
Red Hat Enterprise Linux (RHEL) Server/Client 5.x (Latest Supported 5.8)(32-bit Tuner)
Red Hat Enterprise Linux (RHEL) Server/Client 6.x (Latest Supported 6.2)(32-bit Tuner)
Linux (SUSE) SUSE Linux 11.1 Enterprise Server x64 (32-bit Tuner)
Windows XP Professional (32-bit Tuner) SP 3 for 32-bit (proxies only)1
SP 2 for 64-bit (proxies only)1
Windows Server 2003 x64 (Latest Supported SP2)(32-bit Tuner)
(32-bit Tuner on 64-bit OS): Intel and AMD processors in 32-bit compatible mode. Recommend SP 2
Windows Server 2003 x64 R2 (Latest Supported SP2)(32-bit Tuner)
Windows Server 2008 x64 (Latest Supported SP2)(32-bit Tuner)
Windows Vista Enterprise (Latest Supported SP2)(32-bit Tuner)
Windows 7 Professional/Ultimate/Enterprise (Latest Supported SP1)(32-bit Tuner)
(proxies only)
VMware ESX
GSX
Workstation
NOTE The amount of disk space required to run the tuner is 70–100 MB. For the transmitter, add to that amount the space required by the number and size of channels that you plan to host on the transmitter.
To run properly, the transmitter needs disk space equivalent to about three or four times the total size of your channels, depending on how well your data compresses. This extra space is needed for caching purposes and leads to enhanced performance.
10 Installation Notes May 18, 2012
Requirements for transmitters and proxies
Linux
For a list of required UNIX X11 libraries, see the BMC BladeLogic Client Automation Installation Guide.
Windows
Table 12 Linux requirements for transmitters or proxies
Requirement Description
CPU ■ Pentium 400 MHz (minimum)■ 750 MHz or higher (recommended)
RAM for transmitters
■ 1 GB (minimum)■ 2 GB or higher (recommended)
RAM forproxies
■ 1 GB (minimum)■ 2 GB or higher (recommended)
Disk space for transmitters
■ 105–110 MB■ plus about three or four times the total size of your channels
For more information, see the note about disk space on page 10.
Disk space for proxies
■ 105–110 MB■ plus the size you have configured for the cache.maxSize property,
which is 1 GB by default
Table 13 Windows requirements for transmitters or proxies
Requirement Description
CPU ■ Pentium 400 MHz (minimum)■ 750 MHz or higher (recommended)
RAM for transmitters
■ 1 GB (minimum)■ 2 GB or higher (recommended)
RAM for proxies
■ 1 GB (minimum)■ 2 GB or higher (recommended)
Disk space for transmitters
■ 70–100 MB■ plus about three or four times the total size of your channels
For more information, see the note about disk space on page 10.
Disk space for transmitters hosting the Patch Repository
You might need an additional 30 GB of disk space, depending on the number of patches you store in the repository.
For more information, see “Disk space requirements for Patch Source channels” on page 17.
Disk space for proxies
■ 70–100 MB ■ plus the size you have configured for the cache.maxSize property,
which is 1 GB by default
Version 8.2.01 11
Requirements for the CMS console
Requirements for the CMS console
You can run the following BMC BladeLogic Client Automation modules on console servers:
■ Tuner 8.1.01 or later
■ Tuner Administrator Command Line 8.1.01 or later
■ Infrastructure Administration 8.1.01 or later
■ Common Management Services 8.1.01 or later
■ Schema Manager 8.1.01 or later
■ Report Center 8.1.01 or later
■ Patch Manager 8.1.01 or later
■ Policy Manager (for Desktop Management) 8.1.01 or later
■ Deployment Manager (for Server Management) 7.5.00.008 or later
■ Content Replicator (for Server Management) 8.1.01 or later
■ Deployment Manager Command Line (for Server Management) 7.5.00.008 or later
■ Application Packager (for Server Management, for the Application Packager Task Group page to appear in Deployment Manager) 8.1.01 or later
■ Infrastructure Service 8.1.01 or later
■ Scanner Service (optional) 8.1.01 or later
■ Logging Service (optional) 8.1.00 or later
■ Patch Service (optional) 8.1.00 or later
Table 14 on page 13 identifies the specific versions of the various platforms on which BMC BladeLogic Client Automation web applications are supported, including Report Center, Policy Manager, CMS, Patch Manager, and Deployment Manager.
12 Installation Notes May 18, 2012
Requirements for the CMS console
Linux
For a list of required UNIX X11 libraries, see the BMC BladeLogic Client Automation Installation Guide.
Table 14 Supported platforms for the CMS console
Platform Version Comments
Linux (Red Hat Enterprise)
Red Hat Enterprise Linux (RHEL) Server/Client 5.x (Latest Supported 5.8)(32-bit Tuner)
Red Hat Enterprise Linux (RHEL) Server/Client 6.x (Latest Supported 6.2)(32-bit Tuner)
Linux (SUSE) SUSE Linux 11.1 Enterprise Server x64 (32-bit Tuner)
Windows Windows Server 2003 x64 (Latest Supported SP2)(32-bit Tuner)
(32-bit Tuner on 64-bit OS): Intel and AMD processors in 32-bit compatible mode. Recommend SP 2
Windows Server 2008 x64 R2 (Latest Supported SP1)(32-bit Tuner)
Windows Server 2003 x64 R2 (Latest Supported SP2)(32-bit Tuner)
Windows Server 2008 x64 (Latest Supported SP2)(32-bit Tuner)
Table 15 Linux requirements for the CMS console
Requirement Description
CPU ■ Pentium 266 MHz (minimum)■ 500 MHz or higher (recommended)
RAM ■ 1 GB (minimum)■ 2 GB or higher (recommended)
Disk space for CMS console
200–250 MB, due to inclusion of JREs for all supported platforms
Disk space for Deployment Manager
105–110 MB
Version 8.2.01 13
Requirements for Patch Management source channels
Windows
Requirements for Patch Management source channels
The Patch Management source channels include:
■ Windows Patch Source 8.1.01 or later■ Red Hat Enterprise Linux Patch Source 8.1.01 or later
These Patch Source channels, when installed, contact a website for Microsoft (for Windows) and Red Hat (for Linux) to obtain patch information. Therefore, the machine that hosts one or more of these channels must have IP connectivity to the Internet, either directly or through a proxy. It is recommended that you install the Patch Source channels on a different machine from the one that hosts the CMS console. However, the Patch Source machine and the CMS console machine do need to be able to communicate with each other.
Table 16 Windows requirements for the CMS console
Requirement Description
CPU ■ Pentium 400 MHz (minimum)■ 750 MHz or higher (recommended)
RAM ■ 1 GB (minimum)■ 2 GB or higher (recommended)
Disk space for CMS console
200–250 MB, due to inclusion of JREs for all supported platforms
Disk space for Deployment Manager
70–100 MB
Disk space for Patch Source
Up to 30 GB of disk space, depending on the number of patches you store in the repository
Note: For more information, see “Disk space requirements for Patch Source channels” on page 17.
14 Installation Notes May 18, 2012
Requirements for Patch Management source channels
Table 17 identifies the specific versions of the various platforms on which the Patch Source channels are supported:
For the machine that hosts Windows Patch Source, make sure you have the following run-time files:
Table 17 Supported platforms for Patch Source channels
Platform Version Comments
Linux (Red Hat Enterprise)
Red Hat Enterprise Linux (RHEL) Server/Client 5.x (Latest Supported 5.8)(32-bit Tuner)
Red Hat Enterprise Linux (RHEL) Server/Client 6.x (Latest Supported 6.2)(32-bit Tuner)
Windows Windows Server 2003 x64 (Latest Supported SP2)(32-bit Tuner)
■ Recommend SP 2 (32-bit Tuner on 64-bit OS)
Windows Server 2008 x64 R2 (Latest Supported SP1)(32-bit Tuner)
Windows Server 2003 x64 R2 (Latest Supported SP2)(32-bit Tuner)
Windows Server 2008 x64 (Latest Supported SP2)(32-bit Tuner)
Table 18 Run-time files for machine that hosts Windows Patch Source (part 1 of 2)
Libraries Source
APPHELP.DLLCOMCTL32.DLLCRYPTNET.DLLIMAGEHLP.DLLNETAPI.DLLSHELL32.DLLUSERENV.DLL
Included in all supported platforms
JSCRIPT.DLLMSXML3.DLLMSXML 3.0CLBCATQ.DLLCOMRES.DLL
COM services
NETAPI32.DLLSECUR32.DLLWINTRUST.DLL
WinTrust
Version 8.2.01 15
Requirements for Patch Management source channels
Linux
For a list of required UNIX X11 libraries, see the BMC BladeLogic Client Automation Installation Guide.
Windows
DNSAPI.DLLMSWSOCK.DLLRSADHLP.DLLWINRNR.DLLWS2HELP.DLLWS2_32.DLLWSHTCPIP.DLLWSOCK32.DLL
Winsock2
WLDAP32.DLL ■ 2000 Professional■ XP Professional
WININET.DLL Internet Explorer
Table 19 Linux requirements for Patch Source channels
Requirement Description
CPU ■ Pentium 266 MHz (minimum)■ 500 MHz or higher (recommended)
RAM ■ 1 GB (minimum)■ 2 GB or higher (recommended)
Disk space Files and data are not cached, so you don’t need any disk space.
Note: For more information, see “Disk space requirements for Patch Source channels” on page 17.
Table 20 Windows requirements for Patch Source channels
Requirement Description
CPU ■ Pentium 400 MHz (minimum)■ 750 MHz or higher (recommended)
RAM ■ 1 GB (minimum)■ 2 GB or higher (recommended)
Disk space Approximately 12–30 GB for storing patch information and binaries.
Note: For more information, see “Disk space requirements for Patch Source channels.”
Table 18 Run-time files for machine that hosts Windows Patch Source (part 2 of 2)
Libraries Source
16 Installation Notes May 18, 2012
Requirements for endpoints
Disk space requirements for Patch Source channels
The amount of disk space you need depends to a large extent on whether you choose to download only metadata about the patches most of the time (recommended) and download the actual patch binaries only when you select which patches you want to deploy to endpoints.
If instead you choose a patch download policy of always downloading and packaging all patch binaries when the Patch Repository is updated (which is not recommended), you need the amount of disk space identified in Table 21.
If, however, you use the recommended patch download policy of downloading only patch binaries when you place the patches in a group and publish the group, then the amount of disk space required is greatly reduced. The amount of disk space you need in this case depends on how many patches you publish.
Requirements for endpoints
Endpoints include desktops, laptops, and server endpoints. You can run the following modules on the endpoints:
■ Tuner 8.1.01 or later■ Infrastructure Service 8.1.01 or later■ Scanner Service 8.1.01 or later■ Logging Service (optional) 8.1.01 or later■ Patch Service (optional) 8.1.01 or later
Table 21 Disk space requirements
Patch source channel Disk space
Red Hat Enterprise Patch Source
Files and data are not cached, so you don’t need any disk space on the machine where the Red Hat Enterprise Source is installed and on the machine that hosts the transmitter where patches get published.
Windows Patch Source
■ Approximately 12 GB of disk space on the machine where the Windows Patch Source is installed.
■ 12 GB of disk space for these patches on the machine that hosts the transmitter where the patches get published.
Version 8.2.01 17
Requirements for endpoints
In addition, depending on whether your endpoints are managed with Server Management products or Desktop Management products, you can use:
■ For Desktop Management endpoints: — Policy Service 8.1.01 or later
■ For Server Management endpoints:— Deployment Service 7.5.00.008 or later— Content Replicator 8.1.01 or later
Table 22 identifies the specific versions of the various platforms on which desktop and laptop computers and server endpoints are supported.
Table 22 Supported platforms for endpoints (part 1 of 2)
Platform Version Comments
Linux
(Red Hat Enterprise)
Red Hat Enterprise Linux (RHEL) Server/Client 5.x (Latest Supported 5.8)(32-bit Tuner)
Red Hat Enterprise Linux (RHEL) Server/Client 6.x (Latest Supported 6.2)(32-bit Tuner)
Linux (SUSE) SUSE Linux 11.1 Enterprise Server x64 (32-bit Tuner)
The Patch Service is not supported on this platforms.
Mac OS Xa Mac OSX X86 10.x (Latest Supported 10.7)(32-bit Tuner)
The Patch Service is not supported on this platforms.
Vmware 4 (Linux-Red Hat Enterprise)
Red Hat Enterprise Linux (RHEL) Server/Client 5.x (Latest Supported 5.8)(32-bit Tuner)
Red Hat Enterprise Linux (RHEL) Server/Client 6.x (Latest Supported 6.2)(32-bit Tuner)
18 Installation Notes May 18, 2012
Requirements for endpoints
Windowsb XP Embedded ■ (32-bit Tuner on 32-bit OS): recommend SP 2■ (32-bit Tuner on 64-bit OS): recommend SP 2
Windows XP Professional (32-bit Tuner)
■ Latest Supported SP 3 for 32-bit■ Latest Supported SP 2 for 64-bit
Windows Server 2003 x64 (Latest Supported SP2)(32-bit Tuner)
(32-bit Tuner on 64-bit OS): Intel and AMD processors in 32-bit compatible mode. Recommend SP 2
Windows Server 2003 x64 R2 (Latest Supported SP2)(32-bit Tuner)
Windows Server 2008 x64 R2 (Latest Supported SP1)(32-bit Tuner)
Windows Server 2008 x64 (Latest Supported SP2)(32-bit Tuner)
Windows 7 Professional/Ultimate/Enterprise (Latest Supported SP1)(32-bit Tuner)
HP IPAQ RX3115 with Windows PocketPC 2003
Windows Vista Enterprise (Latest Supported SP2)(32-bit Tuner)
Symbol MC9000 with Microsoft Windows CE.NET
Toshiba E335 with Pocket PC 2002
WePOS (Windows Embedded for Point of Service)
Symbol WT4090 with Windows CE 5.0
Windows CE 4.2
Thin Client with the T5000 series
Windows Mobile 5.1Windows Mobile 6.0
a Mac OS X is supported on desktops and laptops (not server endpoints).b Intel Active Management Technology (Intel AMT) is supported.
Table 22 Supported platforms for endpoints (part 2 of 2)
Platform Version Comments
Version 8.2.01 19
Requirements for endpoints
Linux and VMware (Linux-Red Hat Enterprise)
VMware is used to partition a physical server into multiple virtual machines and to start experiencing the benefits of virtualization. VMware is supported running the BMC BladeLogic Client Automation infrastructure and endpoints. Because of shared resources, however, performance results might vary when you run the BMC BladeLogic Client Automation infrastructure in a virtualized environment.
For a list of required UNIX X11 libraries, see the BMC BladeLogic Client Automation Installation Guide.
Mac OS X
Windows and VMware (Windows)
VMware is used to partition a physical server into multiple virtual machines and to start experiencing the benefits of virtualization.
Table 23 Linux-Red Hat Enterprise and VMware requirements for endpoints
Requirement Description
CPU for desktop endpoints
■ Pentium 133 MHz (minimum)■ 266 MHz or higher (recommended)
CPU for server endpoints
■ Pentium 266 MHz (minimum)■ 500 MHz or higher (recommended)
RAM ■ 1 GB (minimum)■ 2 GB or higher (recommended)
Disk space ■ 105 MB (minimum)■ 110 MB or higher (recommended)■ plus the size of the applications or content you intend to install and
manage
Table 24 Mac OS X requirements for endpoints
Requirement Description
CPU Power PC G4 800 MHz
RAM ■ 1 GB (minimum)■ 2 GB or higher (recommended)
Table 25 Windows and VMWare requirements for endpoints (part 1 of 2)
Requirement Description
CPU for desktop endpoints ■ Pentium 133 MHz (minimum)■ 266 MHz or higher (recommended)
CPU for server endpoints ■ Pentium 266 MHz (minimum)■ 500 MHz or higher (recommended)
20 Installation Notes May 18, 2012
Requirements for endpoints
RAM for desktop endpoints ■ 1 GB (minimum)■ 2 GB or higher (recommended)
RAM for server endpoints ■ 1 GB (minimum)■ 2 GB or higher (recommended)
Disk space ■ 70 MB (minimum)■ 100 MB or higher (recommended)■ plus the size of the applications or content you intend to
install and manage
If you are upgrading from Tuner 4.6.2.2 (with JRE 1.3.1_06) or from Tuner 6.0 (which also uses JRE 1.3.1_10), the size of the upgrade is under 2.5 MB. If you are upgrading from Tuner 4.6.2.2 (with JRE 1.1.8), the size of the upgrade is approximately 22 MB.
■ (If you plan to use Patch Management) Microsoft XML Parser (MSXML)
If the machines are very new and especially if they do not have Internet Explorer installed, make sure MSXML 2.5 (or above) is installed. It consists of the following DLLs: msxml.dll (484 KB) and msxmlr.dll (26 KB). You can download the MSXML toolkit at:
http://www.microsoft.com/en-us/download/details.aspx?id=19662
Table 25 Windows and VMWare requirements for endpoints (part 2 of 2)
Requirement Description
Version 8.2.01 21
Database platforms
Database platformsTable 26 identifies the supported database server platforms for the BMC BladeLogic Client Automation product. For more information about the database requirements, see the BMC BladeLogic Client Automation Installation Guide.
Support for Directory ServicesBBCA 8.2.01 supports the following directory services software:
■ Oracle Directory Server Enterprise Edition 11g
■ Microsoft Windows Server 2003 Active Directory
■ Microsoft Windows Server 2003 Active Directory Application Mode (ADAM)
■ Microsoft Windows Server 2008 Active Directory
■ Windows Server® 2008 Active Directory® Lightweight Directory Services (AD LDS)
Table 26 Database server platforms
Platform Description
Microsoft SQL Server ■ 2005, Enterprise edition, Service Pack 4 (32-bit and 64-bit support), including cluster support.
■ 2008, Enterprise edition, Service Pack 3 (32-bit and 64-bit support)
■ 2008 R2, Service Pack 1 (32-bit and 64-bit support)
■ Non-Enterprise editions of Microsoft SQL Server 2005 and 2008 are not supported.
Oracle® ■ Oracle 10g Standard and Enterprise edition (Release 2, [10.2.0.1.0] recommended)
■ Oracle 10g Standard and Enterprise edition (Release 2 [10.2.0.1.0] recommended) 64-bit support
■ Oracle 11g Standard and Enterprise edition (Release 2 [11.2.0] recommended)
■ Oracle 11g Standard and Enterprise edition (Release 2 [11.2.0] recommended) 64-bit support
■ Oracle RAC 11g (Release 2 [11.2.0] recommended)
Database instances created with the Unicode character set on Oracle 10g and 11g are not supported.
22 Installation Notes May 18, 2012
Support for embedded Software Development Kits (SDKs) platforms
Support for embedded Software Development Kits (SDKs) platforms
BBCA 8.2.01 supports the following embedded SDK platforms:
Support for browsersBBCA 8.2.01 supports the following browsers:
■ Windows Internet Explorer 9.0 or earlier
■ Mozilla FireFox 10 or earlier
■ Google Chrome 16 or earlier
Support for languagesBBCA 8.2.01 supports the following languages:
■ English
■ German
■ French
■ Spanish
SDK platform Embedded SDK
Windows XP Pro (SP2 recommended) Endpoint
Windows 2003 Server (SP1 recommended) Endpoint
Windows Mobile 6.5.3 Endpoint
Symbol MC9000 with Microsoft Windows CE.NET Endpoint
Windows 7 Endpoint
Windows 2008 Endpoint
Linux - Red Hat Client 6.0 Endpoint
Linux - SUSE 11.1 Enterprise Endpoint
Version 8.2.01 23
Support for Java Virtual Machines
Support for Java Virtual MachinesBBCA 8.2.01 supports the following Java Virtual Machines:
■ Java for Mac OSX 1.6.0_24-b07-334 (Mac Intel 10.6 and 10.7)
■ Sun JVM 1.6.0_30 (Windows and Linux)
Customer supportIf you have problems with or questions about a BMC product, see the Customer Support website at http://www.bmc.com/support_home. You can view or download product documents, find answers to frequently asked questions, and download products and maintenance. If you do not have access to the web and you are in the United States or Canada, contact Customer Support at 800 537 1813. Outside the United States or Canada, contact your local BMC office or agent.
© Copyright 2012 BMC Software, Inc.
BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners.
IBM is a registered trademark of International Business Machines Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Oracle is a registered trademark of Oracle Corporation.
Solaris, Sun, Sun Java System Directory Server, and Sun ONE are trademarks or registered trademarks of Oracle Corporation in the U.S. and severalother countries.
UNIX is a registered trademark of The Open Group.
BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted rights notices in the product documentation.
24 Installation Notes May 18, 2012