CA Common Components Release Notes Release 11.3.
This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation is proprietary information of CA and may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA.
CA Technologies Product References This document references the following CA Technologies products: ■ CA Embedded Entitlements Manager (CA EEM) (formerly named eTrust® Identity and Access Management (eTrust IAM)) ■ CA Jobtrac™ Job Management (CA Jobtrac) ■ CA Network and Systems Management (CA NSM) (formerly named Unicenter NSM) ■ CA Scheduler® Job Management (CA Scheduler) ■ CA Universal Job Management Agent (CA UJMA) ■ CA Workload Automation AE (formerly named Unicenter® AutoSys® Job Management
Contents Chapter 1: Welcome 9 CA Common Components DVD .................................................................................................................................... 9 Chapter 2: Known Issues 11 CA Messaging (CAM) in an IPv6 Environment ............................................................................................................ 12 Tomcat Administration Web Interface.....................................................................................................
Chapter 3: Operating System Support 27 Supported UNIX Versions ........................................................................................................................................... 28 Supported Linux Versions........................................................................................................................................... 29 Supported Windows Versions ..............................................................................................................
Chapter 7: General Considerations 59 HAS Considerations - UNIX ......................................................................................................................................... 59 HAS Considerations - Windows .................................................................................................................................. 59 CA EEM Service Name Changes....................................................................................................................
Chapter 1: Welcome Welcome to CA Common Components. This document describes installation considerations, supported operating systems, system requirements, and known issues, if any. For the latest version of the Release Notes, visit http://ca.com/support. For major releases, a full updated documentation set with a bookshelf is provided. You can find the bookshelf containing the Release Notes by searching the Find a Product Documentation Bookshelf section on the Documentation page.
Chapter 2: Known Issues This chapter provides information about issues that are known to exist in this version. This section contains the following topics: CA Messaging (CAM) in an IPv6 Environment (see page 12) Tomcat Administration Web Interface (see page 12) Error Messages in the igateway.
CA Messaging (CAM) in an IPv6 Environment CA Messaging (CAM) in an IPv6 Environment If IPv6 is installed on a computer that already has a CAM service running, CAM must be recycled for it to support IPv6. To recycle CAM from a command line, issue "camclose" followed by "cam start". Tomcat Administration Web Interface The Tomcat Administration Web Interface does not support localized characters in user names and groups. Error Messages in the igateway.log File The igateway.
CAF Error After Deploying the CA Event Agent from IT Client Manager r12 SP1 (UNIX only) CAF Error After Deploying the CA Event Agent from IT Client Manager r12 SP1 (UNIX only) Symptom: After deploying the CA Event Agent from IT Client Manager (Software Delivery), you might get the following error the next time you use SDAgent: caf: error while loading shared libraries: libetpki2.
DIA Setup Failed Error (UNIX only) DIA Setup Failed Error (UNIX only) Symptom: In some CA Event Management upgrades, the CA Distributed Intelligence Architecture (DIA) installation fails with the following error in the DIA logs: The wizard cannot continue because of the following error: could not find wizard home (101) setup has failed Solution: To solve this issue, do the following: 1. Cancel the upgrade process. 2.
PostgreSQL Database Installation Fails (UNIX only) PostgreSQL Database Installation Fails (UNIX only) If a PostgreSQL database has not been uninstalled properly, a socket file and a lock file may remain in the temporary directory (/tmp). If these files are present in the temporary directory and not removed before starting the common components installation, the installer fails to install the PostgreSQL database and the common components installation fails.
CAICCI Stops Responding on AIX Nodes (AIX only) CAICCI Stops Responding on AIX Nodes (AIX only) Symptom: The CAICCI remote daemon process (ccirmtd) and the rmtcntrl status command stop responding on AIX 5.3 or 6.1 nodes. Solution: To solve this problem, do the following: 1. Issue the following command at the command prompt: awservices stop The awservices stop. 2. Open the atservices.ini file that is located at the following path: $AGENTWORKS_DIR/services/config 3.
Coredump Error When Starting and Stopping CA Common Components (AIX only) Coredump Error When Starting and Stopping CA Common Components (AIX only) After you install and start the common components, the CA-cal service fails with the following error messages: unisrvcntr start all Executed CA-emsrvc start.........................................OK Executed CA-help start...........................................OK .CADR_I_DOCINIT Doc/Help server initialized on Sat Nov 20 10:15:01 2010 .
Installation Issue on Linux Platforms Using RPM v4.1.1 (Linux only) Installation Issue on Linux Platforms Using RPM v4.1.1 (Linux only) Symptom: If you want to install CA Event Management or CAICCI in a non-default location on a Linux platform that has RPM v4.1.1 installed on it, you must first create a symbolic link from the default location to the non-default location. Otherwise, the installation fails. Note: All symbolic links must be created from the root user account.
Management Command Center Does Not Launch on Solaris Sparc (x86) After Installation (Solaris only) Management Command Center Does Not Launch on Solaris Sparc (x86) After Installation (Solaris only) For Management Command Center to work, you must update the location where the gtk+ libraries are installed in the LD_LIBRARY_PATH environment variable. For example, on Solaris, the default installation path for gtk is /usr/sfw/lib.
Access Denied for Utility Commands on Microsoft Windows Vista (Windows only) Access Denied for Utility Commands on Microsoft Windows Vista (Windows only) By default, Microsoft Windows Vista gives administrators only standard user privileges through its User Account Control. Because admin privileges are required to install the common components and run most of the commands, you may receive an 'Access is Denied' message when trying to run utility commands from a command prompt.
CA Common Components Installation Does Not Detect Existing Installations (Windows only) CA Common Components Installation Does Not Detect Existing Installations (Windows only) If you select to install Event Management or CAICCI during the common components installation, the installer provides the option to upgrade or remove these common components if the r11 or r11.3 common components are already installed on your computer.
Components Not Selectable for Installation (Windows only) Components Not Selectable for Installation (Windows only) When you attempt to select components during installation, the following message may be displayed preventing the installation process or interview from proceeding: No supported communications protocols have been found. RPC registry key (null) may be missing or damaged. Contact system administrator. This error results from a problem with the configuration of RPC client protocols in Windows.
CA High Availability Service (HAS) and the RMI_Server (Windows only) CA High Availability Service (HAS) and the RMI_Server (Windows only) If you are using HAS to support fault tolerant functionality when Event Management is running in a cluster environment, on a soft failover, you must ensure that the RMI_Server on the device that failed is no longer running. If it is running when the cluster fails back to this node, remote connections cannot be made to the previously running RMI_Server.
Remote Desktop Connection Local Disk UNC Path Not Supported on Microsoft Windows 2003 or Windows XP (Windows only) Remote Desktop Connection Local Disk UNC Path Not Supported on Microsoft Windows 2003 or Windows XP (Windows only) Due to the increased security in Windows installer, installing the common components from a Terminal Services UNC path on Windows 2003 or Windows XP is not supported and generates a 1645 error code.
Use of Non-Microsoft Virtualization Technology (Windows only) Use of Non-Microsoft Virtualization Technology (Windows only) When installing or using the common components inside of a VMware guest Windows operating system, or within other non-Microsoft virtualization technology, be aware that Microsoft does not test and may not support the environment in which the CA software is deployed. Note: For more information, see the Microsoft Knowledge Base.
Chapter 3: Operating System Support CA supports the subsequent operating systems for the duration of their life cycle (as determined by the operating system's manufacturer or until CA announces that we are dropping support). The supporting operating systems are subject to change. For more information about compatibility and to see the latest operating systems supported, visit http://ca.com/support. Notes: ■ For information about CA EEM Release 12.
Supported UNIX Versions Supported UNIX Versions If you want to install a common component on an operating system that is not listed in this topic, do the following: 1. Verify if the common component supports that operating system. Notes: 2. ■ For information about CA EEM Release 12.51 supported operating systems, see the CA Embedded Entitlements Manager Release Notes or visit the CA Embedded Entitlements Manager Product page at http://ca.
Supported Linux Versions Note: For information about CA Workload Automation AE supported operating systems, see the CA Workload Automation AE Release Notes. Supported Linux Versions If you want to install a common component on an operating system that is not listed in this topic, do the following: 1. Verify if the common component supports that operating system. Notes: 2. ■ For information about CA EEM Release 12.
Supported Windows Versions Supported Windows Versions If you want to install a common component on an operating system that is not listed in this topic, do the following: 1. Verify if the common component supports that operating system. Notes: 2. ■ For information about CA EEM Release 12.51 supported operating systems, see the CA Embedded Entitlements Manager Release Notes or visit the CA Embedded Entitlements Manager Product page at http://ca.
Supported Windows Versions ■ Microsoft Windows XP Professional (32-bit version only), with any later maintenance ■ Microsoft Windows Vista (x86 64-bit) for CA NSM remote admin clients Unicenter Managers are not supported on Microsoft client environments (Windows XP, Windows Vista, and Windows 7). Only the Enterprise Management Event Agent client component is supported on those environments.
Chapter 4: IPv6 and Browser Support This chapter provides IPv6 and browser support information for the following common components: ■ SSA ■ Event Management ■ CAICCI ■ Management Command Center Note: For information about CA EEM Release 12.51 browser support, see the CA Embedded Entitlements Manager Release Notes.
Java Browser Support Java Browser Support The common components web applications use Java applications in their web pages and require the following browser support for Java: ■ Built-in Java support in a web browser, if present. If the built-in support for Java is not present, the dashboards require that you install the Java Runtime Environment (JRE) from the Sun Microsystems web site. ■ Install the JRE from the Sun Microsystems web site for the web browser.
Chapter 5: System Requirements This chapter describes the system requirements for the following common components: ■ SSA ■ Event Management ■ CAICCI ■ Management Command Center Note: For information about CA EEM Release 12.51 system requirements, see the CA Embedded Entitlements Manager Release Notes.
Hardware Requirements Hardware Requirements If the computer does not have the minimum resources necessary to support the installed components, you will see messages stating that one or more CA services have failed to start. In some cases, even computers that meet or exceed the necessary hardware requirements may experience this behavior if the combination of software products installed cause a temporary shortage of resources during startup. The services may be operational shortly after the errors appear.
Hardware Requirements Solaris SPARC ■ Processor: SPARC 1.
Software Requirements Software Requirements Depending on your operating environment, the following prerequisite software must be installed for the common components to install and run correctly: AIX ■ xlC.rte.5.0, version 8.0.0.9 through 9.0.0.8 ■ GIMP Toolkit (GTK) 1.2 HP-UX ■ TOUR packages for IPv6 support ■ GTK 1.2 Linux ■ compat-libstdc++-296 or higher for Red Hat Enterprise Linux 4.0 ■ compat-libstdc++-33 or higher for Red Hat Enterprise Linux 5.
GTK Requirements for the Management Command Center GTK Requirements for the Management Command Center The Event Manager includes the Management Command Center, which requires libraries from the GNU Image Manipulation Program (GIMP) Toolkit. The GIMP Toolkit (GTK) libraries are not included in the CA Common Components package.
Database Requirements - UNIX Linux You must apply GTK-1.2.10 patch and its dependencies. The packages are available on your installation media and installed with the currently supported operating systems. The only exception is Red Hat Enterprise Linux Server 5, where the packages must be downloaded externally and then installed.
Database Requirements - Windows Database Requirements - Windows CA EEM uses DxGrid as its data store. The DxGrid data store is installed when you install CA EEM.The installer performs a pre-installation check to determine if an Ingres database exists. If an Ingres database exists, the data in the Ingres database is migrated to the DxGrid data store. Note: eTrust IAM r8.3 use an Ingres database. Event Management requires Microsoft SQL Server, which must be installed before you install Event Management.
su Command on UNIX ■ You can use localized versions of Microsoft SQL Server other than English on any of their respective and matching Windows language versions that CA has certified for use with the common components, with the default code page/character set, or with a code page/character set of 1252 if you are not using specific localized character data for that region, even though you are installing on a localized system of that region.
Kernel Parameter Requirements - HP-UX Installation Kernel Parameter Requirements - HP-UX Installation To install and run the common components on HP-UX, the following kernel parameter requirements must be met or exceeded: ■ The msgmax and msgmnb upper limits must be set to the following values to ensure that the common components function properly: msgmax = 32768 msgmnb = 65535 After the upper limits are set and the parameters are updated during the installation, issue the following command to check whet
Kernel Parameter Requirements - HP-UX Installation 3. Select the following kernel parameters and update the values, if the values in your environment are less than the following required minimum values: max_thread_proc = 512 maxdsiz = 1073741824 maxfiles = 576 maxssiz = 67108864 maxtsiz = 536870912 maxusers = 64 #obsolete for HP-UX 11.
Kernel Parameter Requirements - Linux Installation Kernel Parameter Requirements - Linux Installation To install and run the common components on Linux, the following kernel parameter requirements must be met or exceeded: msgmax = 32768 msgmnb = 65535 msgmni = 128 msgseg = 8192 semmni = 256 semmns = 512 semmsl = 100 shmmni = 512 shmmax = 1073741824 file-max = 8192 threads-max = 65262 To update the kernel parameter values 1.
Kernel Parameter and Resource Controls Requirements - Solaris Installation 2. Edit the /etc/sysctl.conf file by adding or updating the following kernel parameters, if the values in your environment are less than the following recommended values: fs.file-max = 8192 kernel.msgmnb = 65535 kernel.msgmni = 128 kernel.msgmax = 32768 kernel.sem = 100 512 100 256 kernel.shmmni = 512 kernel.shmmax = 1073741824 kernel.threads-max = 65262 3. Issue the following command: /sbin/sysctl -p /etc/sysctl.
tr Command in Unicode Environment on UNIX To update the kernel parameter values in Solaris 9 1. Issue the sysdef command. The kernel parameters of the Solaris computer are displayed. 2. Add the appropriate set and forceload commands (previously mentioned) to the end of the /etc/system file. 3. Restart your computer. The updated kernel parameters take effect. To install and run the common components on Solaris 10, the following resource controls requirements must be met or exceeded: process.
Chapter 6: Installation Considerations This chapter provides information relating to the installation of the common components.
UNIX Installation Considerations Before you install the common components, we recommend that you also review the following important considerations: ■ CA EEM installation considerations (see page 50) ■ Event Management installation considerations (see page 51) ■ UNIX installation directories (see page 52) CA EEM Installation Considerations We recommend that you review the following important considerations before you install CA EEM on UNIX: ■ We recommend that you install CA EEM on a dedicated serve
UNIX Installation Considerations Event Management Installation Considerations We recommend that you review the following important considerations before you install Event Management on UNIX: ■ Event Management can be installed on a dedicated server or on the server where the CA Technologies product is installed. However, Event Management is typically installed on a server other than the one used by the CA Technologies product because of the database size requirements.
UNIX Installation Considerations UNIX Installation Directories All common components must be installed in the same parent directory on a computer. After one common component is installed, you cannot specify another target installation directory to install the other common components. Defined Aliases May Cause the Installation to Fail Defined aliases that alter the native behavior of the operating system commands can cause installation problems.
Windows Installation Considerations Windows Installation Considerations Note: We recommend that you review the Release Notes of the CA Technologies product that uses these common components, in addition to this Release Notes, before installing the common components. We recommend that you review the following items before you install the common components on Windows: ■ On the Choose Install Set page of the installation, the Typical install set installs SSA, CAICCI, and CA EEM.
Windows Installation Considerations CA EEM Installation Considerations We recommend that you review the following important considerations before you install CA EEM on Windows: ■ We recommend that you install CA EEM on a dedicated server. ■ If your environment uses CA EEM with CA Workload Automation AE, all CA Workload Automation AE and CA WCC servers must reference the same instance of CA EEM. Additionally, all members of a CA WCC High Availability group must reference the same instance of CA EEM.
Upgrade Considerations Upgrade Considerations If you have a CA Technologies product installed on your system, a previous release of some of the common components may already be present on your computer. For example, common components may be present if you had installed one or more of the following products: ■ Unicenter Network and Systems Management (NSM) r11.x or CA NSM r11.2 (Linux only) ■ Unicenter AutoSys JM 4.x or r11 or CA Workload Automation AE r11.3 or r11.3 SP1 ■ CA WCC r11.1 SP1, r11.
Highly Available Installations ■ Event Management installed from the current or previous CA Common Components DVD is IPv6 compliant. Previous releases of Event Management (installed from a source other than the CA Common Components DVD) are not IPv6 compliant.
Response File Must Not Be Read-Only Response File Must Not Be Read-Only On UNIX, you cannot use a response file for an unattended installation when the response file is located on a read-only file system or if the response file has the read-only attribute set. The file must be writable because certain values may be altered during installation based on the configuration of the target system.
Chapter 7: General Considerations This chapter provides general information you should know when using the common components. This section contains the following topics: HAS Considerations - UNIX (see page 59) HAS Considerations - Windows (see page 59) CA EEM Service Name Changes (see page 60) HAS Considerations - UNIX Consider the following guidelines for HAS on UNIX: ■ CA Common Components Release 11.3.6 includes High Availability services.
CA EEM Service Name Changes CA EEM Service Name Changes The eTrust Directory - iTechPoz-hostname service in CA EEM r8.3 or r8.4 is named as CA Directory - iTechPoz in CA EEM Release 12.51. Note: The eTrust Directory - iTechPoz-hostname-Router, eTrust Directory Administration Daemon - master, and eTrust Directory SSL daemon - iTechPoz-Server services in CA EEM r8.3 or r8.4 are deprecated.
Chapter 8: Published Fixes The complete list of published bug fixes for this product can be found through Published Solutions on CA Support Online.
Chapter 9: Related Documentation This chapter describes the documents provided with CA Common Components Release 11.3.6 and how to access them. Important! The acknowledgements for third-party components used by CA Common Components are in the acknowledgements.txt file that is located in the root directory of the installed product. Important! The product documentation for future releases of CA Common Components will no longer be available in the product image.
Access the Documentation Access the Documentation To access the CA Common Components documentation in the product image, do the following: ■ On Windows—Go to the Documentation directory and open the Bookshelf.html file. The bookshelf links to all the guides. ■ On UNIX—Use the product DVD. The CA Workload Automation AE bookshelf links to the CA Workload Automation AE, CA WCC, and CA Common Components guides and lets you search across the documentation sets.
