General Server Configurations

Follow the instructions below to configure general server configurations:

1. Install MySQL.
   sudo apt-get install mysql-server mysql-client
2. Set the MySQL root password.
3. Start the MySQL service.
   sudo /etc/init.d/mysql start

4. Log in to the MySQL client as the root user
   mysql -u root -p

   You will be prompted to enter the password. In most systems, the default root password is blank. Press Enter without typing anything, if you have not changed the default root password.

5. In the MySQL prompt, create the database.
   create database EMM_DB;

6. Give authorization for the database to the admin user as follows. Thereafter, exit the MySQL Console.
   GRANT ALL ON EMM_DB.* TO admin@localhost IDENTIFIED BY "<MYSQL ADMIN PASSWORD>";

7. Run the MySQL scripts as follows:
   mysql -u admin -p -DEMM_DB < <PRODUCT_HOME>/dbscripts/emm_mysql.sql;

8. Download the MySQL connector for Java, from http://dev.mysql.com/downloads/connector/j/ and copy the JAR file downloaded to the  <PRODUCT_HOME>/repository/components/lib/ directory.

9. Update the following configuration (i.e., username, password, and more) in the master-datasources.xml file, which is in the  <PRODUCT_HOME>/repository/confg/datasources/ directory.

   <datasource>
        <name>EMM_DB</name>
         <description>The datasource used for EMM</description>
         <jndiConfig>
             <name>jdbc/emmdb</name>
         </jndiConfig>
         <definition type="RDBMS">
              <configuration>
                   <url>jdbc:mysql://localhost:3306/EMM_DB</url>
                   <username>[MySQL username]</username>
                   <password>[MySQL password]</password>
                   <driverClassName>com.mysql.jdbc.Driver</driverClassName>
                   <maxActive>50</maxActive>
                   <maxWait>60000</maxWait>
                   <testOnBorrow>true</testOnBorrow>
                   <validationQuery>SELECT 1</validationQuery>
                   <validationInterval>30000</validationInterval>
              </configuration>
         </definition>
   </datasource>

10. Configure the email parameters as follows:

    1. Create the config.json  file using the template in the  <PRODUCT_HOME>/repository/deployment/server/jaggeryapps/mdm/config/tempConfigs/  directory. Add it inside the <PRODUCT_HOME>/repository/deployment/server/jaggeryapps/mdm/config/ directory and configure the email parameters.
       

    2. Create the  config.json  file using the template in the  <PRODUCT_HOME>/repository/deployment/server/jaggeryapps/mam/config/tempConfigs/  directory. Add it inside the  <PRODUCT_HOME>/repository/deployment/server/jaggeryapps/mam/config/ directory and configure the email parameters.

    3. Rename the mam_config.json.temp file, which is in the <PRODUCT_HOME>/repository/deployment/server/jaggeryapps/publisher/config/ directory, to  mam-config.json and configure the email parameters.

11. Configure the monitor_interval parameter in the config.json file, which is in the <PRODUCT_HOME>/repository/deployment/server/jaggeryapps/mdm/config/ directory. Specify this value in minutes. The EMM server uses this parameter to determine how often the devices enrolled with MDM need to be monitored.  
    For example:
    "monitor_interval" : "2" 

12. Based on the nature of the environment as described in the table below, replace the parameters in the following files: 

    • <PRODUCT_HOME>/repository/deployment/server/jaggeryapps/mdm/config/config.json

    • <PRODUCT_HOME>/repository/deployment/server/jaggeryapps/mam/config/config.json 


    • <PRODUCT_HOME>/repository/deployment/server/jaggeryapps/publisher/config/publisher.json

    • <PRODUCT_HOME>/repository/deployment/server/jaggeryapps/store/config/store.json

      Environment	Parameters
      Development	" %https.ip%"  " %http.ip%"
      Deployment	" %https.host%" "%http.host%"

      The IP address will be automatically fetched from the WSO2 Carbon server.

13. Navigate to the sso-idp-config.xml file, which is in the <PRODUCT_HOME>/repository/conf/ directory and modify the ‘localhost’ to one of the following:

    • Server IP - if working in a testing environment.

    • Domain - if working in a production environment. 

14. For a production deployment uncomment the following code in the carbon.xml file, which is in the  <PRODUCT_HOME>/repository/conf/ directory and enter your organization domain.

    <HostName>www.wso2.org</HostName>
    <MgtHostName>www.wso2.org</MgtHostName>

15. By default, an Identity Provider (IdP) has been bundled with the EMM binary pack. Modify the ‘host’ to the Server IP if you wish to use this default IdP. If you wish to use your own IdP, modify the ‘host’ to the IdP.
16. Create a folder, with a name of your choice <FOLDER_NAME>, in the <PRODUCT_HOME>/repository/deployment/server/jaggeryapps/publisher/  directory.

17. Add the newly created folder name, as the filePreciseLocation element value, in the mam-config.json  file, which is in the <PRODUCT_HOME>/repository/deployment/server/jaggeryapps/publisher/config/  directory.

    {
        'filePreciseLocation': "/upload/",
        "email": {
            "companyName": "",
            "senderAddress": "",
            "emailPassword": "",
        }
    }