System Requirements - CommCell Console as a Stand-Alone Application

Stand-Alone Application | Remote Web-Based Application


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

Operating System

Processor

Windows

Windows Server 2003

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

Windows XP

Microsoft Windows XP Professional 32-bit Editions

Windows Vista

Microsoft Windows Vista 32-bit and x64 Editions

Windows Server 2008

Microsoft Windows Server 2008 32-bit and x64 Editions*

Microsoft Windows Server 2008 R2 Editions*

*Core Editions not supported

Windows 7

Microsoft Windows 7 32-bit and x64 Editions

All Windows-compatible processors supported

 

Linux

CentOS

CentOS 4.6 with glibc 2.3.x

CentOS 5 with glibc 2.5.x

Intel Pentium or compatible minimum required

CentOS 4.6 with glibc 2.3.x

CentOS 5 with glibc 2.5.x

x64

 

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 compatible minimum required

Fedora release 8 with glibc 2.7.x

x64

Red Flag Linux

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

Intel Pentium or compatible minimum required

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

x64

 

Red Hat Enterprise Linux

Red Hat Linux 9.0 32-bit distributions and versions with glibc 2.3.x

Intel Pentium or compatible minimum required

Red Hat Enterprise Linux AS/ES

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

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

Intel Pentium or compatible minimum required

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

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

Intel Itanium

 
 

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

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

x64

Red Hat Enterprise Linux AS 4.0 with glibc 2.3.x

Power PC (Includes IBM System p)

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

Intel Pentium or compatible minimum required

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

Intel Itanium

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

x64

  Red Hat Enterprise Linux Server 5.1 with glibc 2.5.x

Power PC (Includes IBM System p)

SuSE Linux

SuSE Linux Enterprise Server 9 (i586) Edition with glibc 2.3.x

SuSE Linux 9.0 Enterprise Server Edition with glibc 2.3.x

SuSE Linux 9.0 Professional Edition with glibc 2.3.x

SuSE Linux 9.1 Professional with glibc 2.3.x

SuSE Linux 9.2 Professional with glibc 2.3.x

SuSE Linux 9.3 Professional Edition with glibc 2.3.x

SuSE Linux 10 Enterprise Server Edition with glibc 2.4.x

Intel Pentium or compatible minimum required

SuSE Linux 9.0 Enterprise Server Edition with glibc 2.3.x

SuSE Linux 10 Enterprise Server Edition with glibc 2.4.x

Intel Itanium

SuSE Linux 9.0 Enterprise Server Edition with glibc 2.3.x

SuSE Linux 9.2 Professional Edition with glibc 2.3.x

SuSE Linux 9.3 Professional Edition with glibc 2.3.x

SuSE Linux 10 Enterprise Server Edition with glibc 2.4.x

x64

 
SuSE Linux Enterprise Server 9 with glibc-2.3.x

SuSE Linux Enterprise Server 10 with glibc-2.4.x

Power PC (Includes IBM System p)

Ubuntu

Ubuntu 8.04

Intel Pentium or compatible minimum required

Ubuntu 8.04

x64

Mac OS X

Mac OS X v10.4.0

Mac OS X v10.4.1

Mac OS X v10.4.2

Mac OS X v10.4.3

Mac OS X v10.4.4

Mac OS X v10.4.5

Mac OS X v10.4.6

Mac OS X v10.4.7

Mac OS X v10.4.8

Apple Macintosh computer with a PowerPC G4 or G5 processor that supports any of the operating systems identified in this table

Mac OS X Server

Mac OS X Server v10.4.0

Mac OS X Server v10.4.1

Mac OS X Server v10.4.2

Mac OS X Server v10.4.3

Mac OS X Server v10.4.4

Mac OS X Server v10.4.5

Mac OS X Server v10.4.6

Mac OS X Server v10.4.7

Mac OS X Server v10.4.8

Apple Macintosh computer with a PowerPC G4 or G5 processor that supports any of the operating systems identified in this table

Display

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

Memory

32 MB RAM minimum required (Beyond the requirements of the operating system and the console computer)

Hard Disk

65 MB free disk space

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

Miscellaneous

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.

Microsoft Internet Explorer (IE) versions 5.01, 6.0, 7.0, 8.0

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.

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 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.

Notes on CommCell Console Installation

JRE

The software can function with JRE version 1.6.x or higher.

If a JRE version 1.6.0_06 or higher is available, the software will use the existing JRE software.

If JRE version 1.6.0_05 or lower is available, or no JRE version is available at all, you will be prompted to install JRE version 1.6.0_06

You can run CommCell Console as a Remote Web-Based Application without installing the software provided IIS is installed and running on the CommServe computer (or CommCell Console and IIS are running on an alternate computer). However, you must manually install JRE in this case. When running the applet Java™ Runtime Environment (JRE) SE v1.6.0_06 is recommended - can be installed from the software installation disc.

To run the CommCell Console as a Stand-Alone Application on a Macintosh computer, JRE version 1.5 is required.

The following has been observed during the installation of JRE Runtime Environment using the Microsoft Certification Tool.

Some files have no file-type association, description, or icon; they may have a generic icon or are not registered. The following displays those extensions that were Added or Changed but Improperly Registered:

  • .ans - Not Registered - No Filetype - No Icon - No Command
  • .jar - Registered - jarfile - No Icon - "C:\Program Files\Java\jre1.6.0\bin\javaw.exe" -jar "%1" %*
  • .jnlp - Registered - JNLPFile - No Icon - "C:\Program Files\Java\jre1.6.0\bin\javaws.exe" "%1"

No action is required.

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.

If the CommCell Console software is already installed on a computer running IIS version 7.0, the InstallGalaxyWeb utility must be executed on the computer. See Tools and Utilities for more information on this utility.

DISCLAIMER

Minor revisions and/or service packs that are released by application and operating system vendors may, in some cases, affect the working of our software. Although we may list such revisions and/or service packs as “supported” in our System Requirements, changes to the behavior of our software resulting from an application or operating system revision/service pack may be beyond our control. However, we will make every effort to correct such disruption as quickly as possible. When in doubt, please contact your software provider to ensure support for 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.