Silent Install - Unix Agents

Installation

The software can be installed using one of the following methods:

Method 1: Interactive Install

Use this procedure to install the software from the installation package or a network drive on a client computer.

Method 2: Install Using XML File

Use this procedure to install the software on client computer using XML file which allows you to enter installation parameters into a file that is read in by the installation program instead of typing them in response to each installation prompt.

Method 1: Interactive Install

Run the following command from the Software Installation Package.

./cvpkgadd

The product banner and other information is displayed.

Press Enter to continue.

Read the license agreement. Type y and press Enter to continue.

Type 2 and press Enter.

Please select a setup task you want to perform from the list below:

Advance options provide extra setup features such as creating custom package, recording/replaying user selections and installing External Data Connector software.

1) Install data protection agents on this computer

2) Advance options

3) Exit this menu

Your choice: [1]

Press Enter.

Unix Setup Advanced Options

Please select a setup task you want to perform from the list below:

[ Custom Package Creator ]
1) Create a custom install package
[ De-coupled Installer ]
2) Pre-install software Components (De-coupled Mode)
[ Integrated File Archiver ]
3) File System iDataAgent with Archiving Enabler
[ Customized Cluster Agents ]
4) Veritas Cluster Agents
[ Third Party Connector ]
5) Symantec NetBackup Agent
6) NetApp Snap Manager for Oracle
7) NetApp Snap Manager for SAP/Oracle
8) IBM Tivoli Storage Manager
[ Done ]
9) Exit this menu

Your choice: [1]

Press Enter.

Besides general package, you may choose to create one additional native package from the list below.

1) General package only

2) Please also create RPM

3) Please also create solaris native package

4) Please also create hpux native package

5) Please also create Mac package using PackageMaker

6) Please also create APT

7) Exit

Package Type Number [1]

Enter the number to choose a platform.

To select multiple component, enter the number by adding a space.

Please choose one or more platforms to package from the list below.

[ ] 1) Linux X86
[ ] 2) Linux X86_64
[ ] 3) Linux IA64
[ ] 4) Linux PPC64
[ ] 5) Linux S390
[ ] 6) Solaris8/9 SPARC
[ ] 7) Solaris10 SPARC
[ ] 8) Solaris10 X86_64
[ ] 9) Aix PPC
[ ] 10) HP-UX PA-RISC
[ ] 11) HP-UX IA64
[ ] 12) Darwin X86
[ ] 13) FreeBSD4 X86
>) >>>>>>>>>>>> NEXT PAGE >>>>>>>>>>>>

[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]
Enter number(s)/one of "a,n,r,q,d,>,<,?" here: 1

A confirmation screen will mark your choice with an "X". Type "d" for Done, and press Enter.

Please choose one or more platforms to package from the list below.

[X] 1) Linux X86
[ ] 2) Linux X86_64
[ ] 3) Linux IA64
[ ] 4) Linux PPC64
[ ] 5) Linux S390
[ ] 6) Solaris8/9 SPARC
[ ] 7) Solaris10 SPARC
[ ] 8) Solaris10 X86_64
[ ] 9) Aix PPC
[ ] 10) HP-UX PA-RISC
[ ] 11) HP-UX IA64
[ ] 12) Darwin X86
[ ] 13) FreeBSD4 X86
>) >>>>>>>>>>>> NEXT PAGE >>>>>>>>>>>>

[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]
Enter number(s)/one of "a,n,r,q,d,>,<,?" here:

Enter the number corresponding to the IDA module.

To select multiple component, enter the number by adding a space.

Please choose one or more subsystems to package from the list below.

[ ] 1) UNIX File System iDataAgent [1101] [CVGxIDA]
[ ] 2) MediaAgent [1301] [CVGxMA]
[ ] 3) SCSI Driver [1105] [CVGxWA]
[ ] 4) ProxyHost iDataAgent [1102] [CVGxProxyIDA]
[ ] 5) Documentum iDataAgent [1126] [CVGxDctmIDA]
[ ] 6) Oracle iDataAgent [1204] [CVGxOrIDA]
[ ] 7) SAP for Oracle [1205] [CVGxOrSAP]
[ ] 8) SAP for MaxDB [1206] [CVGxSAPMAXDB]
[ ] 9) Informix iDataAgent [1201] [CVGxIfIDA]
[ ] 10) Sybase iDataAgent [1202] [CVGxSybIDA]
[ ] 11) DB2 iDataAgent [1207] [CVGxDB2]
[ ] 12) MySQL iDataAgent [1208] [CVGxMySQL]
[ ] 13) PostGres iDataAgent [1209] [CVGxPostGres]
>) >>>>>>>>>>>> NEXT PAGE >>>>>>>>>>>>

[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]
Enter number(s)/one of "a,n,r,q,d,>,<,?" here: 1

10.

A confirmation screen will mark your choice with an "X".

Type "d" for Done, and press Enter.

Please choose one or more subsystems to package from the list below.

[X] 1) UNIX File System iDataAgent [1101] [CVGxIDA]
[ ] 2) MediaAgent [1301] [CVGxMA]
[ ] 3) SCSI Driver [1105] [CVGxWA]
[ ] 4) ProxyHost iDataAgent [1102] [CVGxProxyIDA]
[ ] 5) Documentum iDataAgent [1126] [CVGxDctmIDA]
[ ] 6) Oracle iDataAgent [1204] [CVGxOrIDA]
[ ] 7) SAP for Oracle [1205] [CVGxOrSAP]
[ ] 8) SAP for MaxDB [1206] [CVGxSAPMAXDB]
[ ] 9) Informix iDataAgent [1201] [CVGxIfIDA]
[ ] 10) Sybase iDataAgent [1202] [CVGxSybIDA]
[ ] 11) DB2 iDataAgent [1207] [CVGxDB2]
[ ] 12) MySQL iDataAgent [1208] [CVGxMySQL]
[ ] 13) PostGres iDataAgent [1209] [CVGxPostGres]
>) >>>>>>>>>>>> NEXT PAGE >>>>>>>>>>>>

[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]
Enter number(s)/one of "a,n,r,q,d,>,<,?" here:

11.

Press Enter.

The native custom package will be created in the following location:

/opt/UnixCustomPackage/.

Save custom package to: [/opt]

12.

Type Yes and press Enter to record the install and continue.

Optionally, you may choose to record install to an xml parameter file now so that you can play it later. The recorded xml will be encapsulated into the custom package and can be used as an answer file in two ways:

(1) from the custom package run "silent_install -p default";

(2) from the native package run native installer(rpm/pkgadd/swinstall...)

You can still perform the above two tasks without custom recording if you choose to use all default parameters.

Do you want to record the install now? [no]

13.

Enter the number corresponding to the IDA module.

To select multiple component, enter the number by adding a space.

Please choose one or more subsystems to package from the list below.

[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]
Enter number(s)/one of "a,n,r,q,d,>,<,?" here:

14.

A confirmation screen will mark your choice with an "X".

Type "d" for Done, and press Enter.

Please choose one or more subsystems to package from the list below.

[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]
Enter number(s)/one of "a,n,r,q,d,>,<,?" here:

15.

Press Enter to accept default value as No.

Type Yes to install Backup Monitor utility. This utility allows you to view the backup job summary from the client computer without opening the CommCell Console. See Monitor - Laptop User for more information.

Do you want to configure the iDataAgent for laptop or desktop backups? [no]

16.

Press Enter.

Do you want to install the agents for restore only without consuming licenses? [no]

17.

Enter the path for installation directory and press Enter.

Please specify where you want us to install Calypso binaries.

It must be a local directory and there should be at least 142MB of free space available. All files will be installed in a "Calypso" subdirectory, so if you enter "/opt", the files will actually be placed into "/opt/Calypso".

Installation Directory:

18.

Enter the path for log directory and press Enter.

Please specify where you want to keep Calypso log files.

It must be a local directory and there should be at least 100MB of free space available. All log files will be created in a "Calypso/Log_Files" subdirectory, so if you enter "/var/log", the logs will actually be placed into "/var/log/Calypso/Log_Files".

Log Directory:

19.

Press Enter to assign user group.

It is recommended that you create a new user group to specify access permission to Calypso processes.

Most of Calypso processes run with root privileges, but some are launched by databases and inherit database access rights. To make sure that registry and log files can be written to by both kinds of processes we can either make such files world-writeable or we can grant write access only to processes belonging to a particular group, e.g. a "Calypso" or a "dba" group.

We highly recommend now that you create a new user group and enter its name in the next setup screen. If you choose not to assign a dedicated group to Calypso processes, you will need to specify the access permissions later.

If you're planning to backup Oracle DB you should use "dba" group.

Would you like to assign a specific group to Calypso? [yes]

20.

Type the Group name and then press Enter.

Please enter the name of the group which will be assigned to all Calypso files and on behalf of which all Calypso processes will run.

In most of the cases it's a good idea to create a dedicated "Calypso" group. However, if you're planning to use Oracle iDataAgent or SAP Agent, you should enter Oracle's "dba" group here.

Group name:

REMINDER

If you are planning to install Calypso Informix, DB2, Sybase or LotusNotes iDataAgent, please make sure to include informix, db2, etc. users into group "galaxy".

Press <ENTER> to continue ...

21.

Type a network TCP port number for the Communications Service (CVD) and press Enter.

Type a network TCP port number for the Client Event Manager Service (EvMgrC) and press Enter.

Every instance of Calypso should use a unique set of network ports to avoid interfering with other instances running on the same machine. The port numbers selected must be from the reserved port number range and have not been registered by another application on this machine.

Please enter the port numbers.

Port Number for CVD:

Port Number for EvMgrC:

22.

If firewall configuration is not required, press Enter.

If the client computer and the CommServe is separated by a firewall, type Yes and press Enter. For firewall options and configuration instructions, see Firewall Configuration and continue with the installation.

Is there a firewall between this client and the CommServe? [no]

23.

Type CommServe Host Name and press Enter.

Please specify hostname of the CommServe below. Make sure the hostname is fully qualified, resolvable by the name services configured on this machine.

CommServe Host Name:

24.

Type the Client Computer Group Name and press Enter.

Please enter one Client Computer Group name for this client to join.

Client Computer Group Name:

25.

Press Enter.

Do you want to configure subclient policy? [no]

26.

Type Storage Policy Name and press Enter.

Please enter a storage policy name for this IDA.

Storage Policy Name:

27.

Type no and press Enter.

This step is applicable only for the installation of DB2 iDataAgent.

In order to complete integration of Calypso with DB2, we need to create links to some Calypso binaries in each of the DB2 instance directories. We can either do it now, or if you prefer, you can run /space/opt/Calypso/iDataAgent/Db2_install.sh script later yourself.

Would you like us to integrate Simpana with DB2 now? [yes] no

28.

Press Enter.

Please select which instance you want to install/replay for this recording:

1) Always install to Instance001
2) Always install to Instance002
3) Always install to Instance003
4) Always install to Instance004
5) Always install to Instance005
6) Always install to Instance006
7) Always install to Instance007
8) Always install to Instance008
9) Always install to Instance009
10) Always install to Instance010
11) Always install to a new instance
12) I want to specify another instance

Your choice: [11]

29.

Enter Yes to create the tar file of Custom Package.

Enter No to continue.

Archiving the custom package in a tar file (Optional)

Optionally, you may choose to tar the package now.

Do you want to create the tar file now? [no] yes

30.

If you entered Yes in the above step, you are advised that the UnixCustomPackage.tar file is created.

Creating /opt/UnixCustomPackage.tar ...Done.

31.

Navigate to the location specified during Custom Package creation.

For example:

/opt/UnixCustomPackage/pkg

32.

Run ./silent_install -p default

Example:

<client_computer>/opt/UnixCustomPackage# ./silent_install -p default

The installation is now complete.

Performing non-interactive Install of the following modules...

* Base Client [1002] [CVGxBase]

* Base0 Client [1003] [CVGxBase0]

* UNIX File System iDataAgent [1101] [CVGxIDA]

Install of the above modules completed successfully.

33.

When you install DB2 iDataAgent on the client computer, once the installation is complete, run the following command from <Calypso>/iDataAgent on the client computer:

Db2_install.sh

For example:

root@orasolaris #./Db2_install.sh

Method 2: Install Using XML File

The silent install feature using XML file allows you to enter installation parameters into a file that is read in by the installation program instead of typing them in response to each installation prompt.

Use the following procedure to install Unix File System iDataAgent on multiple client computers with one command line execution.

Logon to the client computer as root or as a sudo user.

If you are installing the software using a sudo user account, make sure that sudo user account is configured on this computer. For more information, see FAQ - Install.

If your are installing the software from CD, run the following command to mount the CD:

mount -t iso9660,udf /dev/cdrom /mnt/cdrom

Navigate to Software Install Package or mount point

From the Software Install Package (DVD 3) or mount point, copy the silent_answer_example.xml file to user-name directory and file of your choice (e.g., /dir01/user_choice)

Run the following command to copy the sample xml file:

[root@kapow DVD3]# cp silent_answer_example.xml /dir01/silentinstallxml

Open this user-defined file and modify the parameters for installation.

For sample XML file and parameters description, see XML Input File for Silent Install - Unix.

Run the following command to edit the file:

[root@kapow DVD3]# vi /dir01/silentinstallxml

From the Software Installation Package or mount point, run the following command.

./silent_install -param <param_file>

Where:

<param_file> - specifies the name of the file with installation parameters. Make sure to enter the entire path for the file (e.g., /dir01/user_choice).

This installation will use the parameters that you entered in your parameter XML file.

Example:

[root@kapow DVD3]# ./silent_install -param /dir01/silentinstallxml

The installation has completed when a message appears, similar to the example.

Restarting in pdksh-v5.2.14...

Assigning setup GUID... 9-84-kapow.mydomain.company.com-123.23.23.232-8508

Preparing for the setup... READY.

Performing non-interactive Install of the following modules...

* UNIX File System iDataAgent [1101] [CVGxIDA]

Install of the above modules completed successfully.

When you install DB2 iDataAgent on the client computer, once the installation is complete, run the following command from <Calypso>/iDataAgent on the client computer:

Db2_install.sh

For example:

root@orasolaris #./Db2_install.sh

XML Input File for Silent Install

The following is a sample XML file available in the Software Package. For a detailed description on required or optional fields of the XML file, see XML File Parameters.

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<CVInstallManager_ClientSetup Focus="Instance001">
<clientComposition>
<clientInfo>
<client cvdPort="" evmgrcPort="" installDirectory="/opt">
<clientEntity clientName="xyz" hostName="xyz.domain.company.com" physClientName="" physHostName="" vcsServiceGroup="">
</clientEntity>
<jobResulsDir path="/opt">
</jobResulsDir>
</client>
<clientGroups clientGroupName="">
</clientGroups>
<clientProps logFilesLocation="/var/log">
</clientProps>
</clientInfo>
<components>
<1Touch jumpStartDir="/opt/jsdir">
</1Touch>
<cdrDriver logFileLocation="/opt/flrcache" RolCacheMaxDiskSize="3072">
</cdrDriver>
<commonInfo useExistingStoragePolicy="0" globalFilters="0">
<storagePolicyToUse storagePolicyName="" storagePolicyId="">
</storagePolicyToUse>
</commonInfo>
<commserve>
<csdbInfo>
<CommCellUser userName="admin" password="admin">
</CommCellUser>
</csdbInfo>
</commserve>
<componentInfo ComponentId="1101">
</componentInfo>
<dataClassification dcCacheLocation="/opt/dccache">
</dataClassification>
<db2 db2ArchivePath="/opt/ibm/db2/archive" db2RetrievePath="/opt/ibm/db2/retrieve" 
db2AuditErrorPath="/opt/ibm/db2/auditerror">
</db2>
<fileSystem configureForLaptopBackups="0">
<selectedSubclientPolicy subclientPolicyName="" subclientPolicyID="">
</selectedSubclientPolicy>
</fileSystem>
<groupwiseDB>
<userAccount userName="admin" password="admin">
</userAccount>
</groupwiseDB>
<lotusNotesDataArchiver>
<instanceList binaryPath="/opt/ibm/lotus" instanceName="Partition1" path="/opt/ibm/lotus">
</instanceList>
</lotusNotesDataArchiver>
<lotusNotesDB>
<instanceList binaryPath="/opt/ibm/lotus" instanceName="Partition1" path="/opt/domino/datapath1">
</instanceList>
</lotusNotesDB>
<lotusNotesDoc>
<instanceList binaryPath="/opt/ibm/lotus" instanceName="Partition1" path="/opt/domino/datapath1">
</instanceList>
</lotusNotesDoc>
<mediaAgent>
<indexCacheDirectory path="/opt">
</indexCacheDirectory>
</mediaAgent>
<novellDirectoryServices>
<userAccount userName="admin" password="admin">
</userAccount>
</novellDirectoryServices>
<novellFS>
<userAccount userName="admin" password="admin">
</userAccount>
</novellFS>
<oracleSAP sapExeDirectory="/opt/sap">
</oracleSAP>
<OssvNdmp>
<userAccount userName="admin" password="admin">
</userAccount>
</OssvNdmp>
</components>
</clientComposition>
<CommServeInfo>
<CommserveHostInfo hostName="" clientName="">
</CommserveHostInfo>
</CommServeInfo>
<installFlags install32Base="0" install64Base="0" decoupledInstall="0" allowNewerCommserve="0" numberOfStreams="10" unixGroup="" unixOtherAccess="7" restoreOnlyAgents="0" forceIPV4="0" 
singleInterfaceBinding="0" installLatestServicePack="0" loadWAToKernel="0" forceReboot="0" ignoreJobsRunning="0">
<firewallInstall disableFirewall="1" firewallConnectionType="0" firewallConfigFile="" proxyClientName="" proxyHostName="" portNumber="">
</firewallInstall>
</installFlags>
</CVInstallManager_ClientSetup>

Use the following steps to set up firewall configuration during silent install.

Using the text editor, edit the firewall attributes given below in the .XML file depending on your firewall environment.

For detail information on type of firewall connections and firewall parameters, see FirewallInstall.

<firewallInstall disableFirewall="1" firewallConnectionType="0" firewallConfigFile="" proxyClientName="" proxyHostName="" portNumber="">
</firewallInstall>

Additionally, if user needs to add additional parameters during run time, copy the below firewall configuration values using a text editor, and save as .txt file e.g., FwConfig.txt file.

Specify the .txt file path for firewallConfigFile attribute (e.g., firewallConfigFile = "/tmp/FwConfig.txt") in silent_answer_example.xml file.

This will be used to generate the $BaseDIR/FwConfigInstall.txt and used during the installation. After installation the firewall rules will be automatically fetched or updated from the CommServe and saved in the FwConfig.txt by the client.

If this client connects to the CommServe through a port forwarding gateway, specify value 0 for firewallConnectionType attribute in .XML file, copy the below values in firewall configuration .txt file e.g., in FwConfig.txt.
[incoming]

tunnel_port=0

[outgoing]

client_short_name commserve_client_name proto=https cvfwd=commserve_hostname:port type=persistent

If there is HTTP proxy between the client and the CommServe then copy below parameters along with the above parameters.

[http-proxy]

host=http_proxy_hostname

port=http_proxy_port

Example XML Parameter

<firewallInstall disableFirewall="0" firewallConnectionType="0" firewallConfigFile="/tmp/FwConfig.txt" proxyClientName="" proxyHostName="" portNumber=""></firewallInstall>
If CommServe can reach the Client, specify value 1 for firewallConnectionType attribute in .XML file, copy the below values in firewall configuration .txt file
[incoming]

tunnel_port=local_port

[outgoing]

client_short_name commserve_client_name type=passive

Example XML Parameter

<firewallInstall disableFirewall="0" firewallConnectionType="1" firewallConfigFile="/tmp/FwConfig.txt" proxyClientName="" proxyHostName="" portNumber=""></firewallInstall>
If CommServe can reach the client through proxy, specify value 2 for firewallConnectionType attribute in .XML file, copy the below values in firewall configuration .txt file.
[incoming]

tunnel_port=0

[outgoing]

client_short_name short_name_of_proxy_client proto=https cvfwd=host_name_of_proxy_client

client_short_name commserve_client_short_name proxy=short_name_of_proxy_client

If there is HTTP proxy between the client and the CommServe then copy below parameters along with the above parameters.

[http-proxy]

host=http_proxy_hostname

port=http_proxy_port

Example XML Parameter

<firewallInstall disableFirewall="0" firewallConnectionType="2" firewallConfigFile="/tmp/FwConfig.txt" proxyClientName="" proxyHostName="" portNumber=""> </firewallInstall>

Listed below are the required and optional fields in the XML file that the silent install process requires:

Attribute Name

Values

Description

Focus

New

This is the Instance number to which the software will be installed in a multi-instance environment. By default the attribute uses New as a values which automatically defines the existing instance number during install. For example, for first instance the value is defined as instance001, for multiple instance it is defined by the other instance numbers.

clientInfo

cvdPort

8400

Optional. This is the TCP port number for the Communications Service (CVD).

evmgrcPort

8402

Optional. This is the TCP port number for the Client Event Manager Service (EvMgrC).

installDirectory

/opt

Required. This is the directory where you want the Base software and/or iDataAgent installed (e.g., /opt)

clientName

xyz

This is the client name (Name of the Active node in a cluster). (e.g., xyz).

hostName

xyz.domain.company.com

This is the fully qualified domain name of the active node in a cluster. (e.g., xyz.domain.company.com).

physClientName

xyz

Required. This is the name for the physical machine (e.g., xyz)

physHostName

xyz.domain.company.com

Required. This is the name of the physical interface (e.g., xyz.domain.company.com).

vcsServiceGroup

Optional. This is the name of the Veritas Cluster Service Group. Specify the service group name if you are installing in Veritas Cluster environment.

jobResulsDir

/opt

Required. This is the directory where you want the job results to reside (e.g.,/opt)

globalFilters

Optional. This is used to filter out specific directories or files from the backups within the CommCell. The filters are set using the Control Panel in the CommCell Console and, if enabled, they will be effective for the default subclient. Valid values include 2 (use the CommCell-level policy), 1 (on), and 0 (off).

clientGroupName

Optional. This is the name of the client group to which this client will be associated (e.g., client_group1)

logFilesLocation

/var/log

Required. This is the directory where you want the log files to reside (e.g., /var/log).

1Touch

The following parameter pertains only to 1-Touch

jumpStartDir

/opt/jsdir

This is the path of the Jumpstart 'Boot' directory.

ContinuousDataReplicator

The following parameters pertain only to ContinuousDataReplicator

cdrDriver

logFileLocation

/opt/flrcache

This is the path where you want the replication logs files to reside (e.g., /opt/flrcache)

RolCacheMaxDiskSize

3072

This is the amount of log file space required for the caching purpose.

storagePolicyToUse

storagePolicyName

Optional. This is the name of the storage policy you want assigned to the default subclient in the default backup set. Storage policy names are listed on the CommCell Console.

storagePolicyID

Optional. This is the id of the storage policy you want to assigned to the default subclient in the default backup set.

componentInfo

ComponentId

1101

Required. These are the package Id(s) of the components (agents) to be installed, and these parameters are required if they are not specified in the command line. See List of Package Ids for valid values (e.g., 1101).

Component Name	Package ID
Lotus Notes Database iDataAgent	1051
Lotus Notes Document iDataAgent	1052
Domino Mailbox Archiver iDataAgent	1053
File System iDataAgent	1101
ProxyHost iDataAgent	1102
Image Level iDataAgent	1104
WA SCSI driver	1105
Copy Manager Agent	1106
StorageTek EchoView Enabler	1107
File Archiver for Unix	1109
Data Classification	1112
File System Filter Driver	1113
ContinuousDataReplicator	1114
SnapVault Open Systems	1115
SnapVault Open Systems Enabler	1116
NetApp Snapshot Enabler	1117
CommCell Console	1118
1-Touch (Unix)	1119
Recovery Director iDataAgent	1120
Novell GroupWise iDataAgent OES Linux	1121
GroupWise DB on OES	1122
SRM Unix File System Agent	1123
Novell OES Directory Services	1124
Image Level ProxyHost iDataAgent	1125
Documentum iDataAgent	1126
Informix iDataAgent	1201
Sybase iDataAgent	1202
Oracle iDataAgent	1204
Resource Pack	1130
SAP for Oracle iDataAgent	1205
SAP for MAXDB iDataAgent	1206
DB2 iDataAgent	1207
MySQL iDataAgent	1208
PostgreSQL iDataAgent	1209
MediaAgent	1301
NDMP Remote Server Agent	1302
NDMP Restore Enabler	1303
Quick Recovery Agent	1351
QSnap	1401

One or more parameters can be specified (e.g., 1101, 1301)

dataClassification

dcCacheLocation

/opt/dccache

This is the path of the Data Classification cache directory where it will maintain the cache of file system changes.

db2

The following parameters pertain only to DB2 iDataAgent

db2ArchivePath

/opt/ibm/db2/archive

This is the path of the DB2 Archive directory where it stores DB2 archive files.

db2RetrievePath

/opt/ibm/db2/retrieve

This is the path of the DB2 Audit Error directory.

db2AuditErrorPath

/opt/ibm/db2/auditerror

This is the path of the DB2 Retrieve directory where it stores DB2 retrieve files.

fileSystem

The following parameters pertain only to 1-Touch

configureForLaptopBackups

Type 1 to configure iDataAgent for laptop or desktop backups. Once configured, it installs Backup Monitor utility which allows you to view the backup job summary of your client computer. See Monitor -Laptop User for more information.

subclientPolicyName

Optional. This is the name of the subclient policy you want default content to be assigned to the default subclient in the default backup set.

subclientPolicyID

Optional. This is the id of the subclient policy you want default content to be assigned to the default subclient in the default backup set.

lotusNotesDataArchiver

The following parameters pertain only to Lotus Notes Data Archiver

binaryPath

/opt/ibm/lotus

This is the home directory for the partition in which the Lotus Notes software is installed.

instanceName

Partition1

This is the partition name of the computer on which the software is installed.

path

/opt/ibm/lotus

This is the data directory for the partition in which all databases resides.

lotusNotesDB

The following parameters pertain only to Lotus Notes Database

binaryPath

/opt/ibm/lotus

This is the home directory for the partition in which the Lotus Notes software is installed.

instanceName

Partition1

This is the partition name of the computer on which the software is installed.

path

/opt/domino/datapath1

This is the data directory for the partition in which all databases resides.

lotusNotesDoc

The following parameters pertain only to 1-Touch

binaryPath

/opt/ibm/lotus

This is the home directory for the partition in which the Lotus Notes software is installed.

instanceName

Partition1

This is the partition name of the computer on which the software is installed.

path

/opt/domino/datapath1

This is the data directory for the partition in which all databases resides.

mediaAgent

The following parameter pertains only to 1-Touch

indexCacheDirectory path

/opt

This is the location for the MediaAgent's Index Cache.

oracleSAP

The following parameter pertains only to 1-Touch

sapExeDirectory

/opt/sap

This is the path of the SAPEXE directory (e.g., /usr/sap/SYS/exe)

CommServeHostInfo

clientName

Required. The client Name is the short name of the CommServe computer. (e.g., mycomputer)

Do not specify a value for this attribute if you are running a Decoupled Install of the software.

hostName

Required. The host name is the fully qualified domain name of the CommServe computer. Example: mycomputer.mydomain.mycompany.com.

Do not specify a value for this attribute if you are running a Decoupled Install of the software.

installFlags

install32Base

Use value 1 to install 32-bit software on 64-bit operating system.

install64Base

Use value 1 to install 64-bit software on 64-bit operating system.

decoupledInstall

This is used to run a Decoupled Install of the software. Use value 1 to run the decouple install.

allowNewerCommserve

This allows you to install an 8.0 client to an 9.0 CommServe. Use value 1 to install Deprecated Packages to an 9.0 CommServe.

numberOfStreams

This is the number of streams you want allocated (e.g., 10)

This field is only for Solaris clients.

If you enter 0 for this field, the /etc/system configuration file is not updated.

If you enter a value greater than 0, the /etc/system configuration file is updated, and the original version of the file is copied to an /etc/system.gal.PID file (where PID is the installer process ID on the server).

unixGroup

This is the name of the group that will be assigned to all files and on behalf of which all processes will run.

unixOtherAccess

Installer assigns full access rights to root users and its belonging group for all installed Calypso files and its processes. For other users, you can specify the access permission by using this attribute.

This attribute allows you to assign access rights for other users if you are planning to install Calypso agents involving third party software protection.

Use value 0 to 7 which represents the binary numbers e.g., 000(0).... 111(7) to allow read, write or execute permission to other users.

restoreOnlyAgents

Optional. By default the value is set to 0. Use value 1 to install the software without consuming any license.

singleInterfaceBinding

Optional. This is used if you want to bind all services to the specified interface name or IP address. Use value 1 to enforce this capability, 0 to disable it.

installLatestServicePack

Required. This is used to download and install the latest service pack. Use value 1 to download and install the service pack, value 0 to disable the download and install.

loadWAToKernel

Use value 1 to load the WA driver into the kernel and create the device nodes without rebooting the system. By default value is set to 0.

forceReboot

Optional. This is used to reboot the computer if required. Use value 2 to reboot, value 0 to disable.

ignoreJobsRunning

Optional. This is used to ignore the jobs running on the client computer. Use value 1 to ignore the jobs running, value 0 to disable.

firewallInstall

disableFirewall

This is used to specify whether you want to configure firewall settings. Use value 0 to configure firewall settings. Value 1 for no firewall settings.

firewallConnectionType

This is to specify the different type of firewall configuration. The following types of firewall can be configured:

By default, the value is set to 0 where this client connects to the CommServe through a port forwarding gateway.
Use value 1 where CommServe can reach the Client.
Use value 2 where CommServe can be reached through a Proxy.

firewallConfigFile

This is the path of firewall configuration file 9e.g., MyFwConfig.txt)

proxyClientName

This is the short name of the proxy through which the CommServe can be reached.

If you have specified the value 2 in the firewallConnectionType attribute, specify the short name of the proxy client computer.

proxyHostName

This is the hostname of the proxy through which the CommServe can be reached.

If you have specified the value 2 in the firewallConnectionType attribute, specify the host name or the IP address of the proxy computer.

This is the hostname of the proxy through which the CommServe can be reached. If the proxy is behind a port-forwarding gateway, then provide the host name or the IP address of the port-forwarding gateway.

portNumber

This is the port number through which the CommServe can be reached. This number varies depending upon the firewallConnectionType.

If you have specified value 0 for the firewallConnectionType, specify the CommServe HTTP/HTTPs tunnel port number.

If the value is 1, specify local HTTP/HTTPS tunnel port number.

If the value is 2, specify the proxy HTTP/HTTPS tunnel port number.

See Firewall for more information.

Silent Install - Unix Agents

Installation

Method 1: Interactive Install

Method 2: Install Using XML File

Method 1: Interactive Install

Method 2: Install Using XML File

Where:

XML Input File for Silent Install

Example XML File Contents

Firewall Configuration File

Example XML Parameter

Example XML Parameter

Example XML Parameter

XML File Parameters

Component Name

Package ID