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, 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.
Computers running cloud hosts must have UTC times synchronized to within 30 seconds of each other.
The hosts running the cloud partners must be located in the same time zone.
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 (_).
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.
Install Adobe Flash on any cloud host where cloud administration is performed.
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.
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, 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.
On the InstallShield Wizard Completed screen, enable the Configure a new cloud option.
When you click Finish, the installer launches the Cloud Initialization Utility (dbcloudinit.exe) found in the cloud installation directory (for example, C:\Program Files\SQL Anywhere OnDemand 1.0\sa-win64-x64-184.108.40.2066-220.127.116.1187\Bin64\dbcloudinit.exe).
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.
The cloud name must conform to the rules for cloud object names.
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 for the cloud, specify Use FIPS encryption. You cannot alter the FIPS encryption setting once your cloud is created.
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:
The cloud is initialized, your default web browser opens, and you are prompted for your credentials.
Accept the certificate warnings, if prompted.
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).
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.
If you cannot access the Cloud Console, then navigate to https://host-name:port-number/dbcloud/addhost.
dbcloudaddhost.exe 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
High availability is now configured and enabled for your cloud, and cloud setup is complete.
You are now ready to add more hosts, cloud servers, and tenant databases to the cloud.