com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_link3' is unknown.

Running the Product

Owned by Former user (Deleted)
Last updated: Jul 04, 2016
3 min read

To run WSO2 products, you start the product server at the command line. The following sections in this page explains everything you need to know about running the product:

Starting the server

When starting WSO2 EMM, it is mandatory to have an active internet connection; otherwise, the devices will not be able to connect to EMM.

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

On Windows/Linux/Mac OS

To start the server, you run <EMM_HOME>/bin/wso2server.bat (on Windows) or <EMM_HOME>/bin/wso2server.sh (on Linux/Mac OS) from the command prompt as described below. Alternatively, you can install and run the server as a Windows service or Linux service.

  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 <EMM_HOME>/bin/ directory using the Command Prompt.
  3. Execute one of the following commands:
    • To start the server in a typical environment:
      • On Windows:  wso2server.bat --run

      • On Linux/Mac OS:  sh wso2server.sh

    • To start the server in the background mode of Linux: sh wso2server.sh start
      To stop the server running in this mode, you will enter: sh wso2server.sh stop

    • To provide access to the production environment without allowing any user group (including admin) to log into the Management Console:

      • On Windows: wso2server.bat --run -DworkerNode
      • On Linux/Mac OS: sh wso2server.sh -DworkerNode
    • To check for additional options you can use with the startup commands, type -help after the command, such as: 
      sh wso2server.sh -help (see the related topics section at the end of this page).

  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".

On Solaris

To start the server, you run <EMM_HOME>/bin/wso2server.sh from the Command Prompt as described below. 

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

  1. Click Launch -> Run Applications, type dtterm at the Prompt, and then press Enter, to open a Command Prompt.
  2. Navigate to the <EMM_HOME>/bin directory using the Command Prompt.
  3. Execute the following command: bash wso2server.sh

  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".

You need to do the following modification to the <EMM_HOME>/bin/wso2server.sh file, to start the product as a service/nohup mode in Solaris.
  1. Open the <EMM_HOME>/bin/wso2server.sh file in a text editor.
  2. Search for the following occurrences: nohup sh "$CARBON_HOME"/bin/wso2server.sh $args > /dev/null 2>&1 &

  3. Replace those occurrences with the following:  nohup bash "$CARBON_HOME"/bin/wso2server.sh $args > /dev/null 2>&1 &

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

  4. Start the product by following the above instructions.

Accessing the EMM Console

Once the server has started, you can access the WSO2 EMM Consoles. You can also use the EMM Console on this computer or from any other computer connected to the Internet or LAN.

When these pages appear, the web browser will typically display an "insecure connection" message, which requires your confirmation before you can continue.

The EMM consoles are based on the HTTPS protocol, which is a combination of HTTP and SSL protocols. This protocol is generally used to encrypt the traffic from the client to server for security reasons. The certificate it works with is used for encryption only, and does not prove the server identity, so when you try to access these consoles, a warning of untrusted connection is usually displayed. To continue working with this certificate, some steps should be taken to "accept" the certificate before access to the site is permitted. If you are using the Mozilla Firefox browser, this usually occurs only on the first access to the server, after which the certificate is stored in the browser database and marked as trusted. However, with other browsers, the insecure connection warning might be displayed every time you access the server.

This scenario is suitable for testing purposes, or for running the program on the company's internal networks. If you want to make these consoles available to external users, your organization should obtain a certificate signed by a well-known certificate authority, which verifies that the server actually has the name it is accessed by and that this server belongs to the given organization.

If you leave the EMM console unattended, the session will time out. The default timeout value is 15 minutes, but you can change this in the <EMM_HOME>/repository/conf/tomcat/carbon/WEB-INF/web.xml file as follows:

<session-config>
   <session-timeout>15</session-timeout>
</session-config>

Stopping the server

To stop the server, press Ctrl+C in the command window.

What's next

  • Are you an EMM server administrator that looks at installing and starting the EMM server? If yes, go to the Server Administrator guide.
  • Are you an EMM administrator that looks at configuring WSO2 EMM? If yes, go to the EMM Administrator guide.
  • Are you an EMM device owner? If yes, go to the Device Owner guide.
com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links2' is unknown.