Skip to content

Downloading and Starting the Server

This section describes the basic configurations needed for and guides you through on how to start up the server. Before proceeding, make sure to read the system requirements page and have an environnement ready. This guide is based on a Linux based OS.

Get Entgra IoT Platform

Go to the Entgra Contact Us form, and fill in the details to get a copy of the server. If iOS or Windows platforms are needed to be evaluated, please mention this need, as there are separate plugins for these platforms that is not bundled with the server.

Extract .zip File

Extract the zip file to a desired location and go into the extracted folder. (This will be in format entgra-iot-4.x.x). Lets call this folder IOT_HOME folder.

Change IP

If you are setting up the server on a machine with public IP and you need to access the servr with this public IP, the following section is needed.

If you are setting this up on your personal PC/laptop, this step is not mandatory, but there is no harm in following this step. If you decide to ski this step, you can move to Start the Server section.

  1. Using a command prompt, go to IOT_HOME/scripts folder. For example like bellow, cd /Users/username/Downloads/entgra-iot-3.7.0/scripts/
  2. And execute This can be done with following command,./
  3. There are 3 critical values to fill in when executing change-ip.
Input Description
Enter the IoT Core IP that you need to replace (if you are trying out IoT server for the first time this will be the localhost) Provide this as localhost
Enter your current IP Enter the machine IP or the public IP to the machine. This IP must be accessible within the network or over internet. This is because the device we are enrolling later on should be able to access this IP.
Provide common name Same as the current IP, i.e., enter the current IP.

Start the Server

To start the server, go to, IOT_HOME/bin and run ./

You may also start this as a service with ./ start and Stop the service with ./ stop. If you have started as a service, the startup logs can be monitored with the command, tail -f repository/logs/wso2carbon.log

Server start up will end with publishing APIs.