Install, initialize, and configure your cloud.
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, your cloud continues to run. As well, both cloud partners must be running on the same operating system and have Internet connectivity so that they can send usage data to the Usage Server, and they are expected to be running constantly. They also must have access to your SMTP servers to send alert emails.
Time and time zone synchronization You install the cloud host software on three computers. Computers running cloud hosts must have UTC times synchronized to within 30 seconds of each other.
In addition, the two hosts that run the cloud partners must be located in the same time zone.
Host name restrictions The computer names for the three computers can contain only the following characters: a-z, A-Z, 0-9, minus sign (-), period (.), and underscore (_). A host is named according to the computer that it runs on.
Firewalls must allow TCP/IP connections On each host you add to the cloud, configure the firewall to allow TCP/IP connections to the TCP/IP, HTTP, and HTTPS ports used by each cloud server installed on the host. Similarly, configure any firewalls on or between a host that is used to connect to any cloud server to allow TCP/IP connections to the TCP/IP, HTTP, and HTTPS ports used by the cloud server.
If your firewall blocks incoming connections by application, configure your firewall to allow connections to the dbsrv16 executable. Additionally, if your firewall blocks outgoing connections by application, configure your firewall to allow outgoing connections from all cloud executables.
If firewalls are not configured properly, connections could fail, resulting in your cloud not operating correctly.
Cloud Console requires Adobe Flash The Cloud Console, the main user interface for administering the cloud, requires Adobe Flash. Install Adobe Flash on any cloud host where cloud administration is performed.
Windows The My Documents directory for the current user must not be mapped to a network share; otherwise, adding the computer as a new cloud host can silently fail.
Context and remarks
You have designated the three computers that are going to act as cloud partners and cloud arbiter, and are now ready to install the cloud software on the first computer.
You set several passwords during the install process, some of which cannot be changed for the life of the cloud. Consider recording the passwords you specify and storing them in a safe place.
Visit http://response.sybase.com/forms/SQLAOnDemandReg to request SAP Sybase SQL Anywhere, on-demand edition 1.0 Support Package 3. You receive an email containing a registration key and a link for downloading the software.
Download the software and run the installer (setup.exe), accepting all license agreements. When prompted, specify the key that was provided to you when you registered.
On the InstallShield Wizard Completed screen, ensure that Configure a new cloud is selected.
When you click Finish, the installer launches the Cloud Initialization Utility found in the cloud installation directory (for example, C:\Program Files\SQL Anywhere OnDemand 1.0\sa-win32-x86-220.127.116.1195-18.104.22.16896\Bin32\dbcloudinit.exe).
Do not run this utility after your cloud is up and running unless you intend to remove your existing cloud and create a new one. All existing cloud data (including tenant databases) are deleted; this process is irreversible. Before running this utility, you must delete all your hosts except your last cloud partner, and stop the cloud.
In the Cloud name field, give your cloud a name, pick the language you want your cloud to use from the Cloud language dropdown list, and then click Next. The cloud name must conform to the rules for cloud object names. See Restrictions and notes for identifiers and cloud object names.
On the Cloud Administrator Settings screen, provide a full name, new user ID, and a password for the cloud administrator, and then click Next.
On the Host and Port Settings screen, specify dynamic or fixed host addressing. If you are unsure what to specify, check with your system administrator to find out how addressing is configured for your network. For port settings, leave the defaults and click Next. If an error is returned indicating that a port number is already in use, correct the value to an available port.
On the Encryption and Secure Feature Key Settings screen, specify an encryption key and a secure feature key to use for the cloud.
The encryption key is restricted to 7-bit ASCII characters. The encryption key is used to encrypt the cloud. By default, the cloud uses RSA encryption. To use FIPS encryption for the cloud, specify Use FIPS encryption. You cannot alter the FIPS encryption setting once your cloud is created.
The secure feature key is used to enforce tenant database isolation. The secure feature key is restricted to 7-bit ASCII characters and it must have a length between 6 and 128 characters. Secure feature keys cannot:
On the Cloud Certificate Settings screen, specify the certificate to use for the cloud, and then click Next. 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 with the Cloud Console. Unsigned 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, consider using a signed certificate instead.
On the final screen of the Cloud Initialization utility, ensure that Launch the Cloud Console is selected, and then click Finish.
The cloud is initialized, your default web browser opens, and you are prompted to specify the cloud administrator user ID and password.
After you log in, the Cloud Console loads in your default browser ( https://localhost/dbcloud/).
Accept the certificate warning, if prompted.
If the Cloud Console fails to load, try replacing localhost in the URL with the name of your computer and the HTTPS port number.
You are about to create a host install that is used to install cloud software on the computers you have designated to be the second cloud partner and the cloud arbiter. This creates a file called dbcloudaddhost.exe, which you run on the two computers. dbcloudaddhost.exe is not the host install itself. Instead, it is a file that, when run, pulls the host install software you created down from the cloud and runs it.
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 partners, so you create a single host install that you run on the remaining two computers. If bitness is not the same, create two host installs (run Create host install twice), specifying the appropriate bitness. If the arbiter server is to run on a host with a different operating system, then download the cloud software for that operating system to the cloud. See Downloading and redownloading cloud software support packages.
On the computer where you installed the first cloud partner, in the Cloud Console, click Hosts.
On the Hosts panel, click Create host install. If prompted, accept the certificate and continue.
For Host install type, select Multiple use because you are going to use the install more than once: once on the computer that will serve as cloud partner, and once on the computer that will serve as the cloud arbiter.
For Valid for (days), specify the number of days the install is available before it is removed from where it is stored in the cloud, or accept the default (recommended).
For Install can be run on, select Restricted and enter the names and/or IP addresses for the computers that will host the second cloud partner and the cloud arbiter. For security purposes, this method is recommended for adding more than one host to the cloud. Alternatively, you can accept the default, Unrestricted - can be installed on any machine.
For Install version, select the platform/bitness of the host where you are going to run the host install.
For Installation directories, specify the location to install the software and application data to, or accept the defaults (recommended).
For Server ports, accept the default ports that cloud servers will use (recommended), or specify different ports.
Leave Create and start a cloud server on the host selected.
Click Create and Download to create and download the dbcloudaddhost.exe file. The file is downloaded to the default download location for your browser.
Copy dbcloudaddhost.exe to the computers that will host the second cloud partner and the cloud arbiter, and run it on each computer. You are prompted for your cloud user ID and password.
Specify your cloud user name and password when prompted.
dbcloudaddhost.exe performs the following operations:
Downloads the correct cloud software from the cloud to the host you are installing
Installs the cloud host software
Adds the host to the cloud
Creates and starts a cloud server
Cleans up local install files
After you have run dbcloudaddhost.exe on both computers, log in to the Cloud Console to confirm that the cloud now has three cloud servers running.
In the Cloud Console, click Overview.
Locate the High Availability section, and click the Configure high availability link provided beneath it.
In 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.
High availability is now configured and enabled for your cloud, and cloud setup is complete. You can start adding tenant databases to your cloud.
Discuss this page in DocCommentXchange.
|Copyright © 2013, SAP AG or an SAP affiliate company - SAP Sybase SQL Anywhere, on-demand edition 1.0 Support Package 3|