Deployment - SAP for Oracle and SAP for MAXDB iDataAgents


The following sections provide information on SAP for Oracle and SAP for MAXDB iDataAgents deployment:

Install

Pre-Install Select your particular environment from the System Requirements - SAP for Oracle iDataAgent or System Requirements - SAP for MAXDB iDataAgent page to view the minimum requirements for installing the iDataAgent.

Mount the Software Installation Disc provides step-by-step instructions on mounting the installation disc on HP-UX computers.

For Unix platforms, Ensure Restarting of Services Using crontab in the event services go down during a procedure or job.

Install Install the SAP for Oracle or SAP for MAXDB iDataAgent - Windows provides step-by-step instructions for installing the iDataAgent on Windows.

Install the SAP for Oracle iDataAgent - Windows - Clustered Environment - Virtual Server provides step-by-step instructions for installing the iDataAgent on a Windows cluster.

Install the SAP for Oracle or SAP for MAXDB iDataAgent - Unix provides step-by-step instructions for installing the iDataAgent on Unix.

Remote Installs - Unix Agents provides step-by-step instructions for remotely installing the Agent.

Configuration SAP for Oracle or SAP for MAXDB on Windows
  • After the installation you must configure the SAP for Oracle or SAP for MAXDB iDataAgent in order to perform the backup and restore operations. The basic configuration details are described in Create an Instance.

  • Include the Directory Path for backint into the SAP for Oracle User Path.
  • For SAP for MAXDB on Windows, to associate the SAP MAXDB database with the product software, be sure to run the following command:

    dbm_configset -raw BSI_ENV \<software install path>\

    The software install path should be the same as the path provided during the SAP for MAXDB on Windows installation.

  • If you are running multiple stream backups and restores for the SAP for MAXDB iDataAgent, you should define the path for each pipe that is used for the storage media.

    To create Windows pipes, you must use the Windows-specific Visual C functions (e.g., CreateFile(), ReadFile(), etc.). (Windows pipes are not POSIX-compliant.) Windows pipes must be specified in the form "\\. \pipe\[pipe name]". Be sure to issue all of the following commands:

    medium_put BackData2\mem1 \\.\pipe\pipe_mem1 PIPE DATA 0 0 NO NO '' BACK

    medium_put BackData2\mem2 \\.\pipe\pipe_mem2 PIPE DATA 0 0 NO NO '' BACK

    medium_put BackPages2\mem1 \\.\pipe\pipe_mem3 PIPE PAGES 0 0 NO NO '' BACK

    medium_put BackPages2\mem2 \\.\pipe\pipe_mem4 PIPE PAGES 0 0 NO NO '' BACK

    medium_put BackLog\mem1 \\.\pipe\pipe_mem5 PIPE LOG 0 0 NO NO '' BACK

    medium_put CompleteF\mem1 \\.\pipe\pipe_mem5 PIPE File 0 0 NO NO '' BACK

SAP for Oracle or SAP for MAXDB on Unix

  • Before you run backups or restores, create a symbolic link file for the “backint” file
    under the install directory. For example:

    ln -s <software installation path>/iDataAgent/backint /usr/sap/CER/SYS/exe/run/backint

    Then include the /usr/sap/CER/SYS/exe/run directory path into the SAP user path.

  • After the installation you must configure the SAP for Oracle or SAP for MAXDB iDataAgent in order to perform the backup and restore operations. The basic configuration details are described in Create an Instance.

  • For SAP for MAXDB on Unix, to associate the SAP MAXDB database with the product software, be sure to run each of the following commands:

    dbm_configset -raw BSI_ENV /<software install path>/SapMaxDbAgent/backint.conf

    dbm_configset -raw set_variable_0 LD_LIBRARY_PATH=/<software install path>/Base

    dbm_configset -raw set_variable_1 SHLIB_PATH=/<software install path>/Base

    Thereafter, from the root directory, include the following lines in .profile:

    • For AIX and HP-UX:

      SHLIB_PATH=/<software install path>/Base:/<software install path>/Base64

      export SHLIB_PATH

    • For Linux and Solaris:

      LD_LIBRARY_PATH=/<software install path>/Base:/<software install path>/Base64

      export LD_LIBRARY_PATH

  • If you are running multiple stream backups and restores for the SAP for MAXDB iDataAgent, you should define the path for each pipe that is used for the storage media.

    For Unix, you can specify any file path as a pipe, and you can create the pipes in the operating system.  For example:

    medium_put BackData2\mem1 /space/sdb/data/cert1/files/pipe_mem1 PIPE DATA  0 0 NO NO '' BACK

    medium_put BackData2\mem2 /space/sdb/data/cert1/files/pipe_mem2 PIPE DATA 0 0 NO NO '' BACK

    medium_put BackPages2\mem1 /space/sdb/data/cert1/files/pipe_mem3 PIPE PAGES 0 0 NO NO '' BACK

    medium_put BackPages2\mem2 /space/sdb/data/cert1/files/pipe_mem4 PIPE PAGES 0 0 NO NO '' BACK

    medium_put BackLog\mem1 /space/sdb/data/cert1/files/pipe_mem5 PIPE LOG 0 0 NO NO '' BACK

    medium_put CompleteF\mem1 /space/sdb/data/cert1/files/complete FILE DATA 0 0 YES

Upgrade Upgrade the SAP for Oracle or SAP for MAXDB iDataAgent - Windows provides step-by-step instructions for upgrading the iDataAgent on Windows.

Upgrade the SAP iDataAgent - Windows - Clustered Environment - Virtual Server provides step-by-step instructions for upgrade the iDataAgent on a Windows cluster.

Upgrade the SAP for Oracle or SAP for MAXDB iDataAgent - Unix provides step-by-step instructions for upgrading the iDataAgent on Unix.

Silent Upgrade - Unix Agents provides step-by-step instructions to silently upgrade the agent software on Unix using command line instruction.

Automatic Upgrade provides step-by-step instructions for running or scheduling an automatic upgrade of the client or MediaAgent.

Application Upgrades Application Upgrades - SAP for Oracle iDataAgent provides important considerations for the SAP for Oracle iDataAgents when upgrading the iDataAgent computer's operating system.

Uninstall

Uninstall Uninstalling Components provides information on uninstalling CommCell components.

Deconfiguring Agents provides information and links on deconfiguring agents and clients.