Installing in a UNIX or Linux environment

Edit online

Data Protection for SAP is delivered as a single executable file for each operating system. Use the executable file to start the installation wizard and to install the product.

About this task

Packages on the FTP server contain FTP before the operating system designation.
  • For a disk or disk image, the name has the following format: 
    
version-TIV-TSMERPDB2-platform
							
    version-TIV-TSMERPORA-platform
When the file is started, the IBM Storage Protect™ for ERP installation wizard guides you through the procedure. Read the descriptions carefully and follow the guidelines that are displayed on the windows.
Shared libraries have different file extensions on different UNIX™ or Linux™ operating systems. Within the following the section, the file extensions of shared libraries are represented as ext. Replace this text with the extension that applies to your operating system:
Table 1. File Extensions for Shared Libraries
Operating System Extension
AIX® a
HP-UX sl
Linux so
Solaris so

Procedure

  1. Log in as the root user on the SAP database server system.
  2. If the Oracle RMAN interface is used, configure the Data Protection for SAP backup-archive client on your SAP database server as described in the Configuring IBM Storage Protect topic.
  3. Verify that the DISPLAY variable is set to view the installation prompts through a graphical X-Window.
  4. Start the DB2® instance. The installation program makes the necessary updates to the DB2 configuration.
  5. Start the IBM Storage Protect for ERP executable file and follow the installation prompts. appropriate IBM Storage Protect for ERP installation file for your operating system and your Oracle database.
  6. Perform these tasks if the Oracle RMAN interface was selected during the installation process:
    1. Set the IBM Storage Protect for ERP password for Data Protection for SAP as described in the Determining the IBM Storage Protect password method topic.
    2. Make sure /usr/lib is specified in the library path environment of your system.
    3. Customize the SAP backup profile initSID.sap to use RMAN by adding this text:
      backup_dev_type=rman_util
rman_parms="ENV=(XINT_PROFILE=path/initSID.utl,
PROLE_PORT=portnumber,&BR_INFO)"
      Locate the appropriate ProLE port number in the /etc/services file. Look for port name tdpr3ora64.

      If IBM Storage Protect for ERP is not installed in the default path and backups are done by using Oracle RMAN, then the environment variable XINT_NLS_CATALOG_PATH must be added to the parameter rman_pars in the initSID.sap file. The value of XINT_NLS_CATALOG_PATH must be set to the new customized installation path. Otherwise, the message catalog is not found.

  7. If the Oracle RMAN interface was not selected during the installation process, create these links: 
    cd $ORACLE_HOME/rdbms/lib
ln -s /usr/tivoli/tsm/tdp_r3/ora64/libtdp_r3.ext /usr/lib/libobk.ext
ln -s /usr/lib/libobk.ext $ORACLE_HOME/lib/libobk.ext
  8. View the summary in the last page of the installation wizard. The IBM Storage Protect for ERP installation path is displayed in the summary where the installation log file (log.txt) is located.

Results

These modifications are automatically done to your system during installation:

  • An entry is created in /etc/inittab that automatically starts the ProLE daemon on UNIX systems. If upstart is configured, /etc/init/prole_db2.conf is created and upstart starts the "ProLE" daemon.
  • An entry is created in /etc/inittab that automatically starts the ProLE daemon on UNIX systems. If upstart is configured, /etc/init/prole_db2.conf is created and upstart starts the ProLE daemon.
  • The environment variable XINT_PROFILE specifies the IBM Storage Protect for ERP profile that is in the path that is specified for configuration files during installation. The file name is initSID.utl where SID is the DB2 database SID specified during installation.
  • The environment variable TDP_DIR points to the path where IBM Storage Protect for ERP configuration files and process logs are. The default path is profile path/tdplog where profile path is the path that is specified for the IBM Storage Protect for ERP profile during installation.
  • The environment variable XINT_NLS_CATALOG_PATH points to the installation path of IBM Storage Protect for ERP. The message catalog is located under DP for SAP install path/lang where DP for SAP install path is the installation path /usr/tivoli/tsm/tdp_r3/db264.
  • If the DB2 instance is running, the installation program sets the DB2 database configuration parameter VENDOROPT to the IBM Storage Protect for ERP vendor environment file. If VENDOROPT is already set (for example, because of the installation of a previous version), the program uses its value and does not set VENDOROPT. If DB2 log archiving is not to be managed by IBM Storage Protect for ERP, the corresponding database configuration settings are not modified. If DB2 log archiving is to be managed by IBM Storage Protect for ERP, the corresponding DB2 database configuration values are set based on the method that is selected during installation: 
    LOGARCHMETHn  VENDOR:/path/library
LOGARCHOPTn   /path/vendor.env
    If the DB2 instance was not running, you must complete these tasks manually, as described in the Specifying the VENDOROPT parameter and Configuring the DB2 Log Manager topics.
These files are installed in the IBM Storage Protect for ERP installation directory: 
backint
prole
backfm
initSID.bki
libtdp_r3.ext
archive.ksh
backup.ksh
crontab.sample
dsm.opt
dsm.sys
gensortfile.sh 
SanFSsetupFS.sh (AIX only)
inclexcl.list
README
README_TSMERPversionlanguage.html
TIPHINTS
agent.lic (Only after installation from disc or disc image. This file is not 
present in the packages available on the FTP server.)
An entry is created in /etc/inittab that automatically starts the ProLE daemon on UNIX systems.

The EN_US folder is created, which contains the message catalog file tsmerp.cat. The _uninst folder is also created, which contains more files.

These IBM Storage Protect for ERP configuration files are installed in the SAP directory (typically, /oracle/SID/dbs): 
initSID.utl
initSID.bki
agent.lic (copy of file in installation directory)
These files are installed in the IBM Storage Protect for ERP installation directory: 
README
README_TSMERPversionlanguage.html
TIPHINTS
libtdpdb264.a (AIX)
libtdpdb264.so (Linux or Solaris)
ProLE
backom
initSID.utl
SanFSsetupFS.sh (AIX only)
agent.lic (only after installation from disc or disc image)
The folder EN_US is created and it contains the message catalog tsmerp.cat. The _uninst folder is also created, which contains sample files.
These files are installed in the directory where the IBM Storage Protect for ERP configuration files are located: 
initSID.utl
vendor.env
agent.lic (copy of file in installation directory)