1. Documentation
2. 10.3 (Latest) 10.2 10.1 10.0 9.10 9.9 9.8 9.7 9.6 9.5 9.4 9.3 9.2 9.1 9.0 8.2 8.1 8.0 7.6
3. Deployment
4. Cloud
5. Image Architecture

Image Architecture

RapidMiner Server cloud images are implemented as Docker images. We provide a base CentOS image with a Docker layer installed, and we start the additional components, including

• the PostgreSQL database,
• RapidMiner Server, and
• the Job Agent

as three separate Docker containers, using a Docker Compose definition similar to the sample docker-compose.yml configuration provided for the RapidMiner Server Docker image.

The PostgreSQL Docker container functions as the database backend for these images; the database username and password can be found in the file /rapidminer/docker/docker-compose.yml.

Connect to the instances using SSH

Authentication

Both the Amazon AWS and Microsoft Azure cloud platforms provide SSH access to the server instances.

• On Amazon AWS, you can specify the SSH key-pair to use, and the SSH username is fixed (centos) in the image.
• On Microsoft Azure, you can specify the ssh username and password or SSH key within the instance creation wizard.

Filesystem layout

After you connect to the image, you will find the RapidMiner Server files located in the /rapidminer subfolder.

• docker/docker-compose.yml defines the Docker containers, the network connections, the volumes and the required enviroment variables.
• docker/rapidminer-home contains the volume holding the persistent data in the RapidMiner Server home directory.
• docker/pgsql contains the volume holding the persistent data in the the PostgreSQL database.

Configure RapidMiner Server

To configure RapidMiner Server, you follow one of two paths:

• The usual way: the RapidMiner Server home directory page describes the location of extensions, JDBC drivers and licenses.

• The Docker way: in the docker-compose.yml configuration file, you can change the predefined values of the environment variables:

  • Define an external database (e.g. use an RDS instance in AWS) by setting the database-related environment variables in the rapidminer-server service.
  • Redefine the resource allocation for Job Agents by setting the environment variables in the job-agent service.

Restart the Docker instances

After any configuration changes, you should restart RapidMiner Server or the Job Agents by restarting the Docker containers, with (in the simplest cases) the following commands:

sudo docker-compose -f /rapidminer/docker/docker-compose.yml down
sudo docker-compose -f /rapidminer/docker/docker-compose.yml up -d

Check the logs

The logs for RapidMiner Server, Job Agent, or PostgreSQL database are written to the Docker container's console. The logs for RapidMiner Server are also written to rapidminer-home/log/server.log. To check the Docker container console outputs, you can execute one of the following commands (and terminate it by hitting Ctrl+C):

sudo docker-compose -f /rapidminer/docker/docker-compose.yml logs -f rapidminer-server
sudo docker-compose -f /rapidminer/docker/docker-compose.yml logs -f job-agent
sudo docker-compose -f /rapidminer/docker/docker-compose.yml logs -f database