Installing in a Windows environment

Edit online

IBM Storage Protect™ for ERP is delivered as a single executable file (.exe) for each operating system. Packages on the FTP server contain FTP before the operating system designation.

About this task

IBM Storage Protect for ERP for these operating systems is delivered as a single executable file for each operating system. The packages are named as follows:
  • The package name on the disk or the disk image, which is shown in this example: 
    version-TIV-TSMERPDB2-platform
    version-TIV-TSMERPORA-platform

Procedure

  1. Log in as a user with administrator authority on the SAP database server system.
  2. If the RMAN interface is to be installed:
    1. Stop the OracleServiceSID service.
    2. Configure the IBM Storage Protect backup-archive client on your SAP database server as described in the Configure the IBM Storage Protect client options topic.
  3. In Windows™ Explorer, go to the directory where the installation package is located.
  4. If you want the installation program to make updates to the DB2® configuration, start the DB2 instance.
  5. Start the IBM Storage Protect for ERP executable file, and follow the instructions of the installation dialog.
  6. Follow these steps if the Oracle RMAN interface was selected during the installation process:
    1. Set the IBM Storage Protect for ERP password for IBM Storage Protect as described in the Determining the IBM Storage Protect password method topic.
    2. 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 drive:\WINNT\system32\drivers\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.

    3. Restart the Oracle service: OracleServiceSID.
  7. View the summary on the last page of 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

The following modifications are done on your system during installation:
  • The ProLE service is installed and started.
  • An entry is created in %windir%\system32\drivers\etc\services (tdpr3db264).
  • (Optional) The DSMI_DIR, DSMI_CONFIG, and DSMI_LOG environment variables are modified.
  • The DB2 profile registry variable DB2_VENDOR_INI specifies a file that contains theIBM Storage Protect for ERP environment settings for DB2.
  • The XINT_PROFILE environment variable specifies the IBM Storage Protect for ERP profile in the path that is specified during installation. The file name is initSID.utl where SID is the DB2 database SID specified during installation.
  • The TDP_DIR environment variable specifies the directory where IBM Storage Protect for ERP saves the configuration file and creates its process logs. Initially, this path is set to profile path\tdplog where profile path is the path for IBM Storage Protect for ERP profile that is specified 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 that is specified by the user during the installation.
  • 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\tdpdb2.dll
LOGARCHOPTn   drive:\path\vendor.env
    If the DB2 instance is not running, these tasks must be run manually as described in the Specifying the VENDOROPT parameter and Configuring the DB2 Log Manager topics.
The following files are installed in the IBM Storage Protect for ERP installation directory: 
README.txt
README_TSMERPversionlanguage.html
TIPHINTS.txt
tdpdb2.dll
ProLE.exe
backom.exe
initSID.utl
agent.lic (only after installation from disc or disc image)
The _uninst folder is also created, which contains sample files.
These files are installed in the directory where the IBM Storage Protect for ERP profile is located: 
initSID.utl ('SID' is replaced by the DB2 database SID provided during installation)
vendor.env
agent.lic (copy of file in installation directory)
During installation your system is modified in the following way:
  • The ProLE service background process is created.
  • An entry that is required for internal communication is created in %WINDIR%\system32\drivers\etc\services.
These files are installed in the IBM Storage Protect for ERP installation directory: 
backint.exe
prole.exe
orasbt.dll
backfm.exe
backup.cmd
server_a.opt
server_b.opt
inclexcl.list
schedule.sample
dsm.opt
README.txt
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.)
The _uninst folder is also created, which contains more files.
These IBM Storage Protect for ERP configuration files are installed in the SAP directory: 
initSID.bki
initSID.utl
agent.lic (Only after installation from disc or disc image. Not present in the 
Web package.)