Installing in GUI Mode

The installer creates the target directory and installs the selected components into that directory.

The installer for DA server and agents is on the same CD used to install Replication Server. Although you can install one DA server and one DA agent at a time from the installer on a machine, you must run the installer again to install additional DA agents. You cannot install DA server and agents remotely, so you may need to mount the CD and install on more than one machine, depending on your chosen deployment.

  1. Verify that the drive on which you will install the DA server and agents has enough disk space.
  2. Insert the Replication Server DA Option media in the appropriate drive, or download and extract the installation image from the Sybase Product Download Center (SPDC) or the SAP Service Marketplace (SMP).
  3. (Windows) Launch the setup program.
    Note: If the installer does not start automatically, double-click setup.exe or select Start > Run and enter:
    x:\da_installer\setup.exe
    where x: is your CD drive.
    If there is not enough disk space in the temporary disk space directory, set the environment variable TMP to directory_name, where directory_name is the name of the temporary directory to which the installation program writes the temporary installation files. For example:
    set TMP=C:\WINDOWS\Temp
    When specifying the directory_name, include its full path. Reexecute setup.exe.
  4. (UNIX) If you downloaded the product from SPDC or SMP, go to the directory where you extracted the installation image and start the installer:
    ./da_installer/setup.bin

    If you are installing using the CD, mount it and start the installer.

    Note: The location of the mount command is site-specific and may differ from the instructions shown here. If you cannot mount the CD drive using the path shown, check your operating system documentation or contact your system administrator.
    • On HP-UX Itanium:
    1. Log out, log in as “root”, and mount the CD using:
      mount -F cdfs -o ro device_name /mnt/cdrom
    2. Log out as “root” and log in again as “sybase.”
    3. Start the installer:
      cd /cdrom
      ./da_installer/setup.bin
    • On IBM AIX:
    1. Log in as “sybase” and mount the CD:
      mount -v 'cdrfs' -r device_name /mnt/cdrom
    2. Start the installer:
      cd /device_name 
      ./da_installer/setup.bin
    • On Solaris:
    1. The operating system automatically mounts the CD. Log in as “sybase.”
      Note: If you get CD-reading errors, check your operating system kernel to make sure that the ISO 9660 option is turned on.
      If you have previously installed a Sybase product on your system using a CD, the # sign interferes with the installation process. Before using the current CD, either:
      • Restart your system, or,
      • Eject the CD. Delete the Volume Label file in /vol/dsk, and reinsert the CD.
    2. Start the installer:
      cd /cdrom/Volume Label
      ./da_installer/setup.bin
    • On Linux and Linux on POWER:
    1. Log in as “sybase” and mount the CD:
      # mount -t iso9660 /dev/cdrom /mnt/cdrom
    2. Start the installer:
      cd /mnt/cdrom
      ./da_installer/setup.bin
      where:
      • cdrom and /mnt/cdrom is the directory (mount-point) you specified when mounting the CD drive.
      • device_name is the name of the CD device drive.
      • setup.bin is the executable file name to install Replication Server DA Option.
      Set the environment variable IATEMPDIR to tmp_dir, where tmp_dir is the temporary directory to which the installation program writes the temporary installation files. For example, in C shell:
      setenv IATEMPDIR "/usr/bin/tmp_dir"

      When specifying the tmp_dir, include the full path. Reexecute setup.bin.

  5. In the Introduction window, click Next.
  6. Select the geographic location, agree to the license agreement, then click Next.
  7. Specify where to install Replication Server DA Option and click Next.
  8. Select an install set, then click Next:
    Option Description
    Data Assurance server Installs the DA server.
    Data Assurance agent Installs the DA agent. For the best performance, Sybase recommends that you install the DA agent on the machine where your database resides.
  9. Specify the configuration settings for DA server or DA agent:
    DA Server
    Field Description

    Data Assurance Server Instance Name

    Unique name for the DA server instance, which:
    • Cannot be blank
    • Can contain only letters, digits, and underscores
    • Cannot be longer than 30 characters in length
    Default: myserver

    Data Assurance Server Password

    Password for the DA server login da_admin, which:
    • Must be 6 – 30 characters in length
    • Can contain only letters, digits, hyphens, and underscores

    Default: <blank>

    Data Assurance Server Confirm Password

    Password that must match with the chosen password for the installation to continue.

    Default: <blank>

    Data Assurance Server RMI Port

    Java RMI port used by outside applications to connect to the DA server's Java API, such as Sybase Control Center for Data Assurance.

    Default: 4500

    Data Assurance Server TDS Port

    Port used by the command line tool (CLT) or isql utility.

    Default: 4501

    Data Assurance Server DASD Name

    Unique name for the system database, which:
    • Cannot be blank
    • Can contain only letters, digits, and underscores
    • Cannot be longer than 30 characters in length

    Default: dasd

    Data Assurance Server DASD Password

    Password for the system database, which:
    • Must be 6 – 30 characters in length
    • Can contain only letters, digits, hyphens, and underscores

    Default: <blank>

    Data Assurance Server Confirm DASD Password

    Password that must match with the chosen password for the system database password.

    Default: <blank>

    Data Assurance Server DASD Port

    Port on which the system database runs.

    Default: 4503
    Note: By default, the system database is not set up to accept outside connections, so this port is not in use.
    DA Agent
    Field Description

    Data Assurance Agent Instance Name

    Unique name for the DA agent instance, which:
    • Cannot be blank
    • Can contain only letters, digits, and underscores
    • Cannot be longer than 30 characters in length

    Default: myagent

    Data Assurance Agent Password

    (Required) Password for the DA agent login da_admin, which:
    • Must be 6 – 30 characters in length
    • Can contain only letters, digits, hyphens, and underscores

    Default: <blank>

    Data Assurance Agent Confirm Password

    (Required) Password that must match with the chosen password for the installation to continue.

    Default: <blank>

    Data Assurance Agent RMI Port

    Java RMI port used by the DA server to connect to the DA agent.

    Default: 4510

    Data Assurance Agent TDS Port

    Port used by command line tool (CLT) or isql utility.

    Default: 4511

    Data Assurance Agent DTS Port

    Port used by the DA agent to stream data back to the DA server during comparisons.

    Default: 4512

    If you are installing only a DA agent, proceed to step 12.
  10. On the Sybase Software Asset Management License Configuration window, select either:
    Option Description
    Served License If you have a previously deployed license server, enter the host name of the machine where the license server is running and the port number if the port number you are using is not the default.
    Unserved License (Default) Specify a directory where an unserved license is located, or accept the default.

    You can install and use the Replication Server DA Option components without a license for 30 days. To continue using these components after the grace period, obtain valid licenses. See the SySAM Users Guide.

    Click Next.
  11. Set your SySAM e-mail configuration if necessary. Click Next.
  12. Review the installation summary information, and click Install.
  13. When the installation is complete, click Done.
Next
If you encounter an error after installation, check the log files in the log directory: