Running the Product
- Former user (Deleted)
You need to initially configure EMM before attempting to start the servers and run the product. For more information, see the Deployment Guide.
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.
To start the server, you run the script wso2server.bat (on Windows) or wso2server.sh (on Linux/Solaris) from the bin folder. Alternatively, you can install and run the server as a Windows service.
To start and stop the server in the background mode of Linux, run wso2server.sh start and wso2server.sh stop commands.
- Open a command prompt:
- On Windows, choose Start -> Run, type
cmdat the prompt, and press Enter. - On Linux/Solaris, establish a SSH connection to the server or log in to the text Linux console.
Execute one of the following commands, where
<EMM_HOME>is the directory where you installed the product distribution:OS Command Linux/Solaris sh <EMM_HOME>/bin/wso2server.sh
Windows <EMM_HOME>\bin\wso2server.bat --run
If you want to provide access to the production environment without allowing any user group (including admin) to log into the management console, execute one of the following commands:
- On Windows:
<EMM_HOME>\bin\wso2server.bat --run -DworkerNode - On Linux/Solaris:
sh <EMM_HOME>/bin/wso2server.sh -DworkerNode
For additional options you can use with these startup commands, type
-helpafter the command, such as:sh <EMM_HOME>/bin/wso2server.sh -help- On Windows:
The operation log appears. When the product server is running, the log displays the message "WSO2 Carbon started in 'n' seconds".
Running the EMM Consoles
Once the server has started, you can run the EMM Consoles. You can also use the EMM Consoles 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 the 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 consoles 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.