Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SAP SQL Anywhere, on-demand edition 1.0 SP 6 » Installation

Installing the cloud software and configuring the cloud (Linux)

Install, initialize, and configure your cloud.

Prerequisites

The minimum supported configuration for a cloud includes two cloud partners and one cloud arbiter with high availability enabled. Cloud partners are cloud servers that are identical and oversee all activity between hosts and servers in the cloud. Each cloud partner and the cloud arbiter must be on separate computers to ensure that if one computer fails, then your cloud continues to run. Both cloud partners must run constantly and on the same operating system. They must have Internet connectivity and access to your SMTP servers to send alert emails.

  • Timezone synchronization

    Computers running cloud hosts must have UTC times synchronized to within 30 seconds of each other.

  • Host name restrictions

    By default, the host name is the computer name. Host names can only contain the following characters: a-z, A-Z, 0-9, minus sign (-), period (.), and underscore (_).

  • Firewalls must allow TCP/IP connections

    Configure firewalls for cloud hosts to allow TCP/IP connections to the TCP/IP, HTTP, and HTTPS ports used by each cloud server installed on the host. Configure firewalls on or between hosts that are used to connect to cloud servers to allow TCP/IP connections to the TCP/IP, HTTP, and HTTPS ports used by the cloud server.

    If your firewall blocks incoming application connections, then configure the firewall to allow connections to the dbsrv17 executable. If your firewall blocks outgoing application connections, then configure your firewall to allow outgoing connections from all cloud executables.

    If firewalls are not configured properly, then connections may fail.

  • Cloud Console requires Adobe Flash

    Install Adobe Flash on any cloud host where cloud administration is performed.

Context

Run the cloud installer as the root user.

You must provide multiple keys during the initialization of the cloud. These keys are for cloud data and administration only and are unrelated to tenant databases. Tenant databases can have their own individual encryption keys that you provide when the database is added to the cloud.

During the install process, you set several passwords some of which cannot be changed for the life of the cloud. Record your passwords and store them in a safe place.

Procedure

  1. Access the SAP SQL Anywhere, on-demand edition software from SAP and run the installer (setup), accepting all defaults.

    The default cloud installation directory is /opt/saondemand100/.

    After the installation is complete, accept the prompt of the setup program to create a cloud.

    The installer launches the Cloud Initialization utility, which is found in the cloud installation directory. For example, /opt/saondemand100/sa-linux64-x64-17.0.0.1346-1.0.0.5587/bin64s/dbcloudinit).

    Caution

    Do not run this utility after your cloud is running unless you intend to remove your existing cloud and create a new one. All existing cloud data (including tenant databases) is deleted; this process is irreversible. Before running this utility, delete all hosts, except your last cloud partner, and stop the cloud.

  2. Initialize the first cloud partner.
    1. For the Enter the cloud name prompt, give your cloud a name.

      The cloud name must conform to the rules for cloud object names.

    2. For the Enter the two-letter language code for the cloud language prompt, enter the language that you want your cloud to use.
    3. Create the cloud administrator by providing a user ID, password, and full name for the cloud administrator.
    4. For the Select how this host will be addressed by the cloud prompt, specify dynamic or static host addressing. If necessary, check with your system administrator to find out how addressing is configured for your network.
    5. For the Enter the user account name the cloud server should run as prompt, specify which Linux user account the cloud will run from.
      Note Do not run the cloud from the root user account in a production system.
    6. For the port settings, if you specified a non-root user in the previous step, the default port settings for HTTP and HTTPS are: TCP/IP: 2638, HTTP: 40800, HTTPS: 40400. For the root user, the default port settings are: TCP/IP: 2638, HTTP: 80, and HTTPS: 443.

      If an error is returned indicating that a port number is already in use, then change the value to an available port.

    7. On the Encryption and Secure Feature Key Settings screen, specify an encryption key and a secure feature key to use for the cloud.
      • Encryption key

        The encryption key is restricted to 7 bit ASCII characters and is used to encrypt cloud metadata, such as the names of tenant databases and hosts in the cloud, as well as information about cloud users. This key does not encrypt tenant databases.

        By default, the cloud uses RSA encryption. To use FIPS encryption, you can accept Do you want to use FIPS-approved encryption? You cannot alter the FIPS encryption option once the cloud is created.

      • Secure feature key

        The secure feature key enforces tenant database isolation and restricts tenant database users from using secure features. For example, by default the ability to run the xp_read_file system procedure to access files on a cloud host is disabled for tenant database users. To enable this feature, a cloud user must specify the secured feature key.

        The secure feature key is restricted to 7 bit ASCII characters and must be between 6 and 128 characters. Secure feature keys cannot:

        • begin or end with a space or single quote
        • contain backslashes, double quotes, or semicolons
        • contain control characters (characters with an ordinal value of less than 32 or the character value 127)
    8. For the Choose a certificate to be used by the cloud prompt, specify the certificate to use for the cloud. If you do not have a certificate, the cloud creates one for you (RSA encryption with a 2048 bit key).

      The cloud uses certificates to secure communication between cloud servers and the Cloud Console.

    You have now installed the cloud software on a computer and configured the computer to act as the first cloud partner.

  3. Connect to the cloud.
    1. Access the Cloud Console by navigating to https://localhost/dbcloud/. If the Cloud Console fails to load, then try replacing localhost in the URL with the name of your computer and the HTTPS port number (https://cloud-computer-name:https-number.
    2. Connect to the cloud by specifying your cloud administrator user ID and password.

      Accept the certificate warning, if prompted.

      Note Self-signed certificates can cause certificate warnings in your browser when you attempt to access the Cloud Console. It is safe to ignore these warnings in a development environment. However, for increased security in your production environment, use a signed certificate.

      After you connect, the Cloud Console loads in your default browser (https://localhost/dbcloud/). If the Cloud Console fails to load, then try replacing localhost in the URL with the name of your computer and the HTTPS port number (https://cloud-computer-name:https-number/.

    3. On the cloud Overview panel, click Add licenses and enter the core license keys you received from SAP. Click OK.
  4. Install cloud software on the second cloud partner and the cloud arbiter and configure high availability for the cloud.

    Each host install is specific to an operating system and bitness. The following instructions assume that the computer you designate for the cloud arbiter has the same operating system and bitness as the cloud partners, so that you can create a single host install and run it on the remaining two computers. If the bitness is not the same, then create two host installs (run Create host install twice), specifying the appropriate bitness. If the arbiter server is on a host with a different operating system, then download the cloud software package for that operating system, add it to the cloud, and create another host install for the arbiter.

    1. In the Cloud Console, on the computer where you installed the first cloud partner, navigate to the Hosts panel.
    2. Click Create host install. If prompted, accept the certificate and continue.

      If you cannot access the Cloud Console, then navigate to https://host-name:port-number/dbcloud/addhost.

    3. For Host install type, select Multiple use because you are going to use the install more than once: once on the cloud partner computer, and once on the cloud arbiter computer.
    4. For Valid for (days), specify the number of days that the install is available before it is removed from the cloud, or accept the default (recommended).
    5. For Install can be run on, select Restricted and enter the names and/or IP addresses of the computers that will host the second cloud partner and the cloud arbiter (recommended), or accept the default: Unrestricted - can be installed on any machine.
    6. For Install version, select the platform/bitness of the host where you are going to run the host install.
    7. For Installation directories, specify the location to install the software and cloud data to, or accept the defaults (recommended).
    8. For Server ports, accept the default ports that the cloud servers will use (recommended), or specify different ports.
    9. Leave Create and start a cloud server on the host selected.
    10. Click Create and Download to create and download the dbcloudaddhost file. The file is downloaded to the default download location for your browser.
    11. Run the following command:
      chmod +x dbcloudaddhost
    12. Copy dbcloudaddhost to the computers that will host the second cloud partner and the cloud arbiter, and run it.
    13. Specify your cloud user ID and password when prompted.

      dbcloudaddhost performs the following operations:

      • Downloads the correct cloud software from the cloud to the host you are installing

      • Installs the cloud software on the host

      • Adds the host to the cloud

      • Creates and starts a cloud server

      • Cleans up local install files

    14. After you have run dbcloudaddhost on both computers, log in to the Cloud Console to confirm that the cloud now has three cloud servers running.
    15. In the Cloud Console, click Overview.
    16. Under High Availability, click Configure high availability.
    17. On the Cloud High Availability window, set the cloud partner and the cloud arbiter by selecting the cloud servers running on the hosts you installed, then click Finish.

Results

High availability is now configured and enabled for your cloud, and cloud setup is complete.

Next Steps

You are now ready to add more hosts, cloud servers, and tenant databases to the cloud.