You are viewing the RapidMiner Server documentation for version 9.2 - Check here for latest version
RapidMiner Server on Microsoft Azure
From the link below, you can start a RapidMiner Server Virtual Machine, either via a pay-as-you-go plan or via a bring-your-own-license (BYOL) plan.
For details of the installation, continue reading.
The RapidMiner Server Virtual Machine
Please follow these steps to start a RapidMiner Server Azure Virtual Machine:
- Log in to your Azure account and go to your Azure Portal Dashboard.
- Click on the Virtual Machines in the left menu and select the Add button.
- Search for "RapidMiner" in the Images
- Select the required version of the Image
- Continue with the Create Virtual Machine Wizard by adding the name of the Virtual Machine. Enter your user name and SSH credentials and select (or create a new) Resource Group, where your Virtual Machine will be created.
- Choose an instance size. We recommend using at least 7 Gb of RAM for RapidMiner Server.
- Configure the Instance Details by selecting the networking parameters. Make sure you enable public IP or consult your network administrator about your networking configuration. Check the Security group settings and ensure that ports 8080 and 1081 are open for RapidMiner Server and 22 for SSH.
- Finally review and purchase your virtual machine.
Log in to RapidMiner Server
After the virtual machine is ready, continue with the following steps:
- Using a browser connect to the virtual machine's port 8080. (e.g. http://public.ip:8080) or consult your network administrator about how to access your instance.
- Check your virtual machine's name on the Azure Portal.
- On the login screen please use the username admin and use the name of your virtual machine as password.
- If you chose a pay-as-you-go AMI, that’s all you need to do. You can already connect to it from a browser or from your RapidMiner Studio. If you chose a bring-your-own-license AMI, then you’ll be presented with a page where you need to paste your license. After that, you’ll need to restart the VM.
Next: the image architecture