System Requirements - CommCell Console

Stand Alone Application Remote Web Based Features  

The following requirements are for the CommCell Console as a Stand-Alone Application:

Operating System

Processor

Linux

Debian

Debian 5.x with glibc 2.7.x

Intel Pentium, x64 or compatible processors

Fedora

Fedora release 8 with glibc 2.7.x

Intel Pentium or x64 processors

Red Flag Linux

Red Flag Linux AS 5.0 64-bit with glibc 2.3.x

x64

Red Flag Linux AS 4.1 32-bit with glibc 2.3.x

Intel Pentium or compatible minimum required

Red Hat Enterprise Linux AS/ES

Red Hat Linux AS 4.0 with glibc 2.3.x

Power PC (Includes IBM System p)

Red Hat Enterprise Linux AS/ES 4.0 with glibc 2.3.x

Intel Pentium, Itanium, x64 or compatible processors

Red Hat Enterprise Linux/CentOS

Red Hat Enterprise Linux/CentOS Server 5.1 with glibc 2.5.x

Power PC (Includes IBM System p)

Red Hat Enterprise Linux/CentOS 5 Advanced Platform with glibc 2.5.x

Intel Pentium, Itanium, x64 or compatible processors

SuSE Linux (SLES)

SuSE Linux 10 Enterprise Server with glibc-2.4.x

Power PC (Includes IBM System p)

SuSE Linux 10 Enterprise Server Edition with glibc 2.4.x

Intel Pentium, Itanium, x64 or compatible processors

Ubuntu

Ubuntu 8.04

Intel Pentium or x64 processors

Mac OS X Server

Mac OS X v10.4.8

Apple Macintosh computer that supports any of the operating systems identified in this table

Mac OS X v10.4.7

Apple Macintosh computer that supports any of the operating systems identified in this table

Mac OS X v10.4.6

Apple Macintosh computer that supports any of the operating systems identified in this table

Mac OS X v10.4.5

Apple Macintosh computer that supports any of the operating systems identified in this table

Mac OS X v10.4.4

Apple Macintosh computer that supports any of the operating systems identified in this table

Mac OS X v10.4.3

Apple Macintosh computer that supports any of the operating systems identified in this table

Mac OS X v10.4.2

Apple Macintosh computer that supports any of the operating systems identified in this table

Mac OS X v10.4.1

Apple Macintosh computer that supports any of the operating systems identified in this table

Mac OS X Server v10.4.8

Apple Macintosh computer that supports any of the operating systems identified in this table

Mac OS X Server v10.4.7

Apple Macintosh computer that supports any of the operating systems identified in this table

Mac OS X Server v10.4.6

Apple Macintosh computer that supports any of the operating systems identified in this table

Mac OS X Server v10.4.5

Apple Macintosh computer that supports any of the operating systems identified in this table

Mac OS X Server v10.4.4

Apple Macintosh computer that supports any of the operating systems identified in this table

Mac OS X Server v10.4.3

Apple Macintosh computer that supports any of the operating systems identified in this table

Mac OS X Server v10.4.2

Apple Macintosh computer that supports any of the operating systems identified in this table

Mac OS X Server v10.4.1

Apple Macintosh computer that supports any of the operating systems identified in this table

Mac OS X Server v10.4.0

Apple Macintosh computer that supports any of the operating systems identified in this table

Windows

Windows 8

Microsoft Windows 8 Editions

All Windows-compatible processors supported

Windows 7

Microsoft Windows 7 32-bit and x64 Editions

All Windows-compatible processors supported

Windows 2008

Microsoft Windows Server 2008 32-bit and x64 Editions

All Windows-compatible processors supported

Windows Vista

Microsoft Windows Vista 32-bit and x64 Editions

All Windows-compatible processors supported

Windows 2003

Microsoft Windows Server 2003 32-bit and x64 Editions with a minimum of Service Pack 1

All Windows-compatible processors supported

Windows XP

Microsoft Windows XP Professional 32-bit Editions with a minimum of Service Pack 3

All Windows-compatible processors supported

Hard Drive

65 MB free disk space

763 MB of temp space required for install or upgrade (where the temp folder resides)

Memory

32 MB RAM minimum required beyond the requirements of the operating system and running applications

Display

The minimum resolution required to properly display the CommCell Console is 1280x1024.

The graphical icons in the CommCell Console cannot be displayed in VGA mode. This affects the appearance of the toolbar and the CommCell tree in the CommCell Browser. Also, some table of contents is not displayed correctly.

Miscellaneous

Network

TCP/IP Services configured on the computer.
The CommCell Console supports Internet Protocol versions 4 and 6 (IPv4 and IPv6). See Internet Protocols for more information.

Internet Explorer

Microsoft Internet Explorer (IE) version 8.0, 9.0

.NET Framework

.NET Framework 2.0 is automatically installed. Note that .NET Framework 2.0 can co-exist with other versions of this software.

Microsoft Visual C++

Microsoft Visual C++ 2008 Redistributable Package is automatically installed. Note that Visual C++ 2008 Redistributable Package can co-exist with other versions of this software.

SELinux

If you have SELinux enabled on the client computer, create the SELinux policy module as a root user before performing a backup. The SELinux Development package must be installed on the client.

To create an SELinux policy module, perform the following steps as user "root":

  1. Create the following files in the /usr/share/selinux/devel directory:
File Name Content of the File
<directory>/<file_name>.te

where:

<directory> is /usr/share/selinux/devel

<file_name> is the name of the Unix file, created to save the policy module statement. It is a good idea to use the same name for policy module and the file.

For example: When you are creating a policy module for backup_IDA application, you can use the following file name: backup_IDA.te

 

The content of the file should be as follows:

policy_module(<name>,<version>)

##############################

where:

<name> is the name of the policy module. You can give any unique name to the policy module, such as a process or application name.

<version> is the version of the policy module. It can be any number, such as 1.0.0.

For Example: While creating a policy module for the backup_IDA application, you can use the following content.

policy_module(backup_IDA,1.0.0)

<directory>/<file_name>.fc

where:

<directory> is /usr/share/selinux/devel

<file_name> is the name of the Unix file, created to save the policy module statement. It is a good idea to use the same name for policy module and the file.

For example: When you are creating a policy module for backup_IDA application, you can use the following file name: backup_IDA.fc

 

The content of the file should be as follows:

Note that the following list of files is not exhaustive. If the process fails to launch, check /var/log/messages. Also, if required, add it to the following list of files.

/opt/<software installation directory>/Base/libCTreeWrapper.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libCVMAGuiImplgso -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libdb2locale.so.1 -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libdb2osse.so.1 -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libDb2Sbt.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libdb2trcapi.so.1 -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libDrDatabase.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libIndexing.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libSnooper.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

 

  1. Create the policy file from command line. Use the following command. Ensure that you give the following commands in the /usr/share/selinux/devel directory.

[root]# make backup_IDA.pp

Compiling targeted backup_IDA module

/usr/bin/checkmodule: loading policy configuration from tmp/backup_IDA.tmp

/usr/bin/checkmodule: policy configuration loaded

/usr/bin/checkmodule: writing binary representation (version 6) to tmp/backup_IDA.mod

Creating targeted backup_IDA.pp policy package

rm tmp/backup_IDA.mod tmp/backup_IDA.mod.fc

[root]# semodule -i backup_IDA.pp

[root]#

  1. Execute the policy module. Use the following command:

[root]# restorecon -R /opt/<software installation directory>

SELinux is now configured to work with this application.

Java Support

The software supports Java 7 or higher*.

  Java 7 versions are supported with Calypso Service Pack 8 or higher. Previous service pack versions do not fully support this version.

If a JRE version 1.7.0_17 or higher is available, the software will use the existing JRE software.

If a JRE version lower than 1.7.0_17 is available, or no JRE version is available at all, you will be prompted to install JRE version 1.7.0_17

*The Backup Time selection in the Advanced Options area of the Find dialog box is not compatible with Java 7 or higher.

IIS

IIS must be installed on the CommServe computer to remotely access the CommCell Console as a Remote Web-Based Application.

If an alternate computer is used as the IIS server, the alternate computer must:

  • be in the same domain as the CommServe.
  • have the CommCell Console installed.

See Web Administration for more information.

If the CommCell Console software is going to be installed on a computer running IIS version 7.0 and 7.5, the following software components must be installed and configured along with all default components on the computer prior to the CommCell Console installation:

  • ASP
  • CGI
  • ISAPI Extensions
  • IIS 6 Management Capability

Note that on Windows Vista and Windows Server 2008 computers, these components will be automatically installed if not already installed on the computer.

DISCLAIMER

Minor revisions and/or service packs that are released by application and operating system vendors are supported by our software but may not be individually listed in our System Requirements. We will provide information on any known caveat for the revisions and/or service packs. In some cases, these revisions and/or service packs affect the working of our software. Changes to the behavior of our software resulting from an application or operating system revision/service pack may be beyond our control. The older releases of our software may not support the platforms supported in the current release. However, we will make every effort to correct the behavior in the current or future releases when necessary. Please contact your Software Provider for any problem with a specific application or operating system.

Additional considerations regarding minimum requirements and End of Life policies from application and operating system vendors are also applicable