SQL Anywhere, on-demand edition Installation and Setup
Module 1 - Installation and Setup
In this module, you will walk through the installation of the software, as well as the addition of hosts and
servers to the on-demand edition environment.
This is the first module in the SAP Sybase SQL Anywhere, on-demand edition Tutorial series.
On-demand edition Cloud Architecture
The SAP Sybase SQL Anywhere, on-demand edition is intended to be installed on at least three hosts,
where a host is a machine (either physical or virtual). Two cloud partners and a cloud arbiter must be
installed, one on each host. The cloud partners must be installed on hosts that have internet
connectivity. The cloud arbiter oversees the two cloud partners and monitors their states. This
architecture is designed so that as long as at least two of these three servers are running, the cloud will
continue to function. For example, if one of the cloud partners has been disconnected, the cloud arbiter
will become aware of the issue and ensures that the other, still functioning, cloud partner takes over. If
the cloud arbiter is the server that runs into an error in the cloud, the cloud partners are not affected
and can continue to function. The cloud arbiter does not require internet connectivity and requires only
network connection to the two cloud partners.
These servers, as well as any other servers added to the cloud are referred to as cloud servers, which
run your tenant databases.
The cloud partners will connect to the SAP Sybase SQL Anywhere on-demand edition Usage Server over
the internet to transfer your usage information. If the connection fails, an alert will appear in the Cloud
On your first host, you will install and initialize the first cloud partner. Initialization of the cloud will
create and start up the cloud administration infrastructure and start a Cloud Agent service on the host
machine. Recall that this host must have connectivity to the internet.
To setup and start your on-demand edition cloud, follow the instructions provided at
Once you have your minimum cloud architecture setup, you are ready to start creating additional cloud
servers and adding tenant databases. Cloud servers can be added to any host in the cloud. Tenant
databases added to the cloud reside on these cloud servers. Tenant databases can be moved either
manually or when tags and cloud rules are in effect.
For the purposes of these modules and for simplicity, there are only two hosts used in the screenshots
and examples. The two hosts will have a cloud server each and tenant databases will be added to them
throughout the modules.
Add Cloud Servers
In the Cloud Console, click Servers in the left hand navigation pane. You will see that a default server has
been created on your first host. To add a server to another host:
- Click Create. This will show a dialog, allowing you to choose what host to add the server to and the number of servers you want to create. Choose a host, specify the number of servers to create, and click Next.
- Choose the page size to use for the server and software version by choosing from the dropdown menus and click Next.
- Specify port numbers for the server and click Finish.
- The new server will be added and will appear in the list of servers. You may have to wait a few seconds for the server status to be updated.
Stopping Cloud Servers
To stop a cloud server from the Cloud Console:
- Click Servers in the left hand navigation pane.
- Select the checkbox for the server you want to stop.
- Click Stop.
Deleting Cloud Servers
To delete a cloud server from the Cloud Console, you must stop the cloud server first. After the cloud server has been stopped, you can proceed to delete it:
- Click Servers in the left hand navigation pane.
- Select the checkbox for the server you want to remove.
- Click Delete.
Stop and Restart the Cloud
To stop your cloud:
- Click Overview in the left hand navigation pane
- Click Stop the cloud in the Other Actions section.
- Specify whether the cloud should be stopped unconditionally and click Finish.
After you verify that you want to stop the cloud, the Cloud Console goes offline, and your browser will redirect you to on-demand edition cloud documentation on how to restart the cloud. The cloud is now in the process of stopping. Stopping the cloud may take a few minutes to complete.
To restart a cloud that has been temporarily stopped, you must restart the SQL Anywhere Cloud Agent services running on all three hosts that run the cloud partners and the cloud arbiter. Ensure that the cloud environment variables are set. To restart the services, in a command prompt:
To determine the name of the Agent, run:
First, you will need to stop the Agent, run:
dbsvc –x <cloudagent-name>
Then to start the Agent up again, run:
dbsvc –u <cloudagent-name> -y
The Cloud Agent must be restarted on all three hosts, the two cloud partners and the cloud arbiter. Once you have completed this step on the three hosts, you can log in to the Cloud Console and restart all other cloud servers and tenant databases.