This documentation is for WSO2 IoT Server 3.1.0. View the documentation for the latest release.
Page Comparison - Running the Product (v.13 vs v.14) - IoT Server 3.1.0 - WSO2 Documentation

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Tip
titleBefore you begin

If you wish to try out the Raspberry Pi and Arduino sample plugins, in the WSO2 IoT Server console, navigate to the WSO2 IoTS directory and run the device-plugins-deployer.xml file.
Example: 

Code Block
cd <IOTS_HOME>/samples
mvn clean install -f device-plugins-deployer.xml

NOTE: Android, Windows and Android Sense are included in the server by default. You will need to configure WSO2 IoT Server to try out iOS.

Follow the instructions below to start your WSO2 product based on the Operating System you use:

Localtab Group
Localtab
activetrue
titleWindows/Linux/Mac OS

Follow the steps given below:

  1. Open a command prompt by following the instructions below:
    • On Windows: Click Start > Run, type cmd at the prompt, and then press Enter.
    • On Linux/Mac OS: Establish an SSH connection to the server, log on to the text Linux console, or open a terminal window.
  2. Navigate to the <IoTS_HOME>/bin directory using the Command Prompt to start the WSO2 IoT Server core, broker and analytics profiles all at ones.

  3. Start the profiles in the following order:
    1. Start the broker profile, which corresponds to the WSO2 Message Broker profile.

      Localtab Group
      Localtab
      activetrue
      titleLinux/Mac OS
      Code Block
      cd <IOTS_HOME>/bin
      ./broker.sh
      Localtab
      titleWindows
      Code Block
      cd <IOTS_HOME>\bin
      .\broker.bat

      The default port assigned for the broker is 9446.

    2. Start the core profile, which corresponds to the WSO2 Connected Device Management Framework (WSO2 CDMF) profile.

      Localtab Group
      Localtab
      activetrue
      titleLinux/Mac OS
      Code Block
      cd <IOTS_HOME>/bin
      ./iot-server.sh
      Localtab
      titleWindows
      Code Block
      cd <IOTS_HOME>\bin
      .\iot-server.bat

      The default port assigned for the core is 9443. 

    3. Start the analytics profile, which corresponds to the WSO2 Data Analytics Server profile.

      Localtab Group
      Localtab
      activetrue
      titleLinux/Mac OS
      Code Block
      cd <IOTS_HOME>/bin
      ./analytics.sh
      Localtab
      titleWindows
      Code Block
      cd <IOTS_HOME>\bin
      .\analytics.bat

      The default port assigned for analytics is 9445.

    The operation log appears in the command window. When the product server has successfully started, the log displays the message WSO2 Carbon started in 'n' seconds

Localtab
titleSolaris

Follow the steps given below:

Note

Following instructions are tested on an Oracle Solaris 10 8/11 x86 environment.

  1. Anchor
    instructions
    instructions
    Click Launch > Run Applications, type dtterm at the Prompt, and then press Enter, to open a Command Prompt.
  2. Navigate to the <IOTS_HOME>/bin directory using the Command Prompt.
  3. Start the profiles in the following order:
    1. Start the broker profile, which corresponds to the WSO2 Message Broker profile.

      Code Block
      cd <IOTS_HOME>/bin
      ./broker.sh

      The default port assigned for the broker is 9446.

    2. Start the core profile, which corresponds to the WSO2 Carbon Device Management Framework (CDMF) profile.

      Code Block
      cd <IOTS_HOME>/bin
      ./iot-server.sh

      The default port assigned for the core is 9443. 

    3. Start the analytics profile, which corresponds to the WSO2 Data Analytics Server profile.

      Code Block
      cd <IOTS_HOME>/bin
      ./analytics.sh

      The default port assigned for analytics is 9445.

  4. The operation log appears in the command window. When the product server has successfully started, the log displays the message WSO2 Carbon started in 'n' seconds.

Info

You need to do the following modification to the respective .sh files, to start the product as a service/nohup mode in Solaris.

  1. Open the .sh file of the respective profile:
    • broker profile - <IOTS_HOME>/wso2/broker/bin/wso2server.sh
    • core profile - <IOTS_HOME>/bin/iot-server.sh
    • analytics profile - <IOTS_HOME>/wso2/analytics/bin/wso2server.sh
  2. Search for the following occurrences:

    Panel
    Localtab Group
    Localtab
    titlebroker/analytics profile
    Code Block
    nohup sh $CARBON_HOME/bin/wso2server.sh $args > /dev/null 2>&1 &
    Localtab
    titlecore profile
    Code Block
    nohup sh $CARBON_HOME/bin/iot-server.sh $args > /dev/null 2>&1 &
  3. Replace those occurrences with the following:

    Panel
    Localtab Group
    Localtab
    titlebroker/analytics profile
    Code Block
    nohup bash $CARBON_HOME/bin/wso2server.sh $args > /dev/null 2>&1 &
    Localtab
    titlecore profile
    Code Block
    nohup bash $CARBON_HOME/bin/iot-server.sh $args > /dev/null 2>&1 &
    Tip

    The only change is replacing sh with bash. This is required only for Solaris.

  4. Start the product by following the above instructions.

...