Installing in a Distributed Environment Using the Console

Install the ESP Server and Studio with any combination of external and enterprise adapters on various machines within your network.

  1. From the command line, navigate to the directory where the installation file (setup.bin) resides.
  2. Type ./setup.bin -i console and press Enter.
  3. When prompted, press Enter to continue.
  4. Select the installation location. To accept the default location, press Enter. To specify a custom location:
    1. Enter an absolute path to the location. Select a file path that does not contain any spaces.
    2. Press Enter.
    3. Type Y or N to indicate whether the location is correct.
      Note: The console accepts both Y and Yes as affirmative, and everything else as a negative response.
    4. If the directory you specified does not exist, the installer asks if you want to create it. Press Y. If the directory already exists, the installer warns you that any software in the folder will be replaced.
      In either case, press Enter to continue.
  5. Enter 2 to select the Custom install set. Press Enter.
  6. Enter the numbers corresponding to the features you want to select or deselect for installation, separated by a comma with no space. If you select the Studio for installation, also select the Server.
    The installer selects specific components by default. Selected components are indicated by an X, deselected components are indicated by a blank. Enter the number of a component to toggle the current selection. When finished, press Enter.
    Note: If the target installation machine hosts other Sybase products, you may have already installed the SySAM License Utilities. You need not install them again.
  7. If, in step 6, you selected external adapters only (no enterprise adapters, Server, or Studio), the installer summarizes your installation preferences and prompts you to install. Click Enter to continue, then Enter again to complete the installation. Otherwise, continue to step 8.
  8. If you have a previous version installed to the selected location, a message indicates that you can uninstall the previous version, or overwrite it. Enter your selection and press Enter.
  9. Indicate whether you want to install a licensed version or an evaluation version and press Enter.
    Note: If you install the evaluation version, the software is active for 30 days, after which you will be prompted for a valid license key. Proceed to step 13.
  10. If you are installing a licensed version, select one of these options:
    License Type Process
    Specify License Keys
    • Type 1 and press Enter.
    • Enter the license key.
    • Press Enter.
    • Once your license key is validated successfully, press Enter to continue installation.

    If you are using a served license and receive an error that the installer detects a SySAM server already running on your machine, click Previous to return to the SySAM License Entry panel and select the Previously Deployed License Server option.

    If you enter an invalid key, you are prompted by a warning message. You cannot proceed until you provide a valid key or select a different licensing option.
    Previously Deployed License Server
    • Type 2 and press Enter.
    • Press Enter to accept the default host name, or enter the Host Name and Port Number.

    If the license server file is not found, you receive a warning message indicating that the installer cannot verify a license server running on the selected host. When prompted, enter Y to reenter the license server or n to select a different licensing option.
    Continue Without a License Key Type 3 and press Enter. At the prompt asking if you want to continue, press Enter.

    The software is active for a 30-day grace period, after which you are prompted for a valid license key.
  11. Indicate the product license type you want to configure and press Enter.
  12. Indicate whether you want to configure SySAM e-mail alerts. To configure alerts:
    1. Enter the SMTP server host that handles your e-mail.
    2. Enter the SMTP server port.
    3. Enter the e-mail address of the person or group from which e-mail messages are sent.
    4. Enter the e-mail addresses of the default recipients.
    5. Enter the default severity level (informational, warning, or error) for e-mail messages.
    Note: To change the SySAM alert settings after installation, edit the lines in the ESP_HOME/sysam/esp_license.prop file:
    • email.smtp.host=smtp
    • email.smtp.port=25
    • email.sender=sender@domain.com
    • email.recipients=user@domain.com
    • email.severity=INFORMATIONAL

    Setting email.severity to NONE disables e-mail alerts, causing all other lines to be ignored. To enable e-mail alerts, set email.severity with ERROR, WARNING, or INFORMATIONAL. Replace SMTP with your SMTP host name, 25 with the port number of your SMTP mail server, sender@domain.com with your e-mail address, and user@domain.com with e-mail recipients. Separate multiple e-mail recipients with a comma (,).

  13. Enter the number corresponding to your geographic location and press Enter.
  14. Read through the license agreement. Press Enter as necessary to move through the text. Stop reading the text at any point by typing back and pressing Enter.
  15. Indicate that you agree to the license terms and press Enter.
    Note: If you are installing enterprise adapters only, repeat steps 9 through 15 for each enterprise adapter you are installing. Then proceed to step 20.
  16. Configure cluster information:
    1. Create a name for the new node. If the node will be part of an existing multi-node cluster, all nodes names in the cluster must be unique.
    2. Enter the host name of the machine hosting this cluster node. Use the default localhost only if this is a single node cluster that will only be accessed from within the machine you are installing on.
    3. Enter the RPC port for the cluster node. The Studio, SDK, and various other product tools use this port to access the cluster.
    4. Indicate whether the RPC port supports connections through Secure Sockets Layer (SSL) or not. When you enable SSL, connections to the cluster use HTTPS rather than HTTP. If you are creating a new cluster, you can decide whether you want to use SSL or not. If you are connecting to an existing cluster, ensure this selection matches the configuration of the existing cluster.
    5. Enter the cache port for the node. The cluster cache is an internal cache for sharing cluster state and configuration information. It is for internal use only.
    6. Create a name for your new cluster, or enter the name of an existing cluster.
    7. Indicate whether you want to provide a password for accessing the cluster now. All nodes within the cluster use the same password. If you select No, you are prompted to provide a password when you start the cluster node.
      If you select Yes, enter a password for the cluster and press Enter. If you are connecting to an existing cluster, use the password defined for that cluster.
    8. Enter the number corresponding to the security type to apply to your cluster If you are connecting to an existing cluster, select the security type the existing cluster uses, and provide credentials for that cluster:
      1 - LDAP: Provides LDAP authentication. Enter information for the following fields as determined by your LDAP implementation:
      • Server type
      • Provider URL
      • Default search base
      • Authentication scope
      2 - Kerberos: Provides Kerberos authentication. Enter the following information as determined by your Kerberos implementation:
      • Realm
      • KDC
      3 - RSA: Provides RSA authentication. The following RSA values are set by default:
      • Digester
      • Provider
      • Algorithm
      4 - None: Provides open security, which allows any name and password combination to log in. Therefore, no additional configuration is required.
    Note: After installation, you can modify your cluster configuration to add additional nodes and clusters. For information, see the Administrators Guide.
  17. Indicate the location of the keystore file or press Enter to accept the default.
    A keystore is a third-party application that generates encryption keys. These keys encrypt/decrypt data within Event Stream Processor, such as passwords required to read or write to databases. By default, the keystore type is set to JKS and the algorithm is RSA.
  18. Indicate whether you want to provide a password to access the keystore file and key. If you select No, you are prompted for one at startup. If you select Yes, enter a password for the keystore. If you are connecting to an existing cluster, use the keystore password already defined for that cluster.
  19. Enter an absolute path to the workspace location for Studio projects, or press Enter to accept the default location.
  20. If you are installing enterprise adapters, repeat steps 9 through 15 for each adapter. Otherwise, continue to step 22.
  21. At the pre-installation summary, confirm that you have enough disk space for the installation. Press Enter to continue.
  22. Press Enter to install the files.
  23. When installation is complete, press Enter.
  24. If you installed the Studio, indicate whether you want to run it immediately or not. Press Enter.
    If you run the Studio immediately, the Studio launches and you exit the installer. If you select to run the Studio later, you exit the installer.
Tip: If Studio does not start, try manually deleting the .metadata folder in the workspace directory.
Parent topic: Performing a Distributed Installation