This page takes you through the steps for upgrading from EMM 1.0.1 version to EMM 1.1.0. For more information on release versions, see the Release Matrix.
...
The
mdm-config.xml
, which is in the<EMM_HOME>/repository/conf/
directory, has been renamed toemm-config.xml
in EMM 1.1.0 together with the following tags:EMM 1.0.1 Tag EMM 1.1.0 Tag <ios-enroll-url>
<iOSEnrollURL>
<ios-profile-url>
<iOSProfileURL>
<ios-checkin-url>
<iOSCheckinURL>
<ios-server-url>
<iOSServerURL>
<ios-device-property-post-url>
<TokenURL>
The following configurations in the
mdm-config.xml
file, which is in the<EMM_HOME>/repository/conf/
directory, have been removed in EMM 1.1.0 and these configurations need to be configured via the iOS Settings page in the EMM Console.Code Block <!-- iOS APNS configurations --> <ios-apns-cert-path>[APNS-CERTIFICATE-PATH]</ios-apns-cert-path> <ios-apns-cert-password>[APNS-PASSWORD]</ios-apns-cert-password> <ios-apns-production-mode>true</ios-apns-production-mode> <!-- iOS MDM APNS configurations --> <ios-mdm-apns-cert-path>[MDM-APNS-CERTIFICATE-PATH]</ios-mdm-apns-cert-path> <ios-mdm-apns-cert-password>[MDM-APNS-PASSWORD]</ios-mdm-apns-cert-password> <ios-mdm-apns-production-mode>true</ios-mdm-apns-production-mode> <!-- iOS mdm topic id --> <ios-mdm-topic-id>[MDM-TOPIC-ID]</ios-mdm-topic-id>
The following configuration that was in the
<EMM-1.0.1_HOME>\repository\deployment\server\jaggerya
pps\mdm\config\config.json
file has been added to the<EMM-1.1.0_HOME>/repository/conf/emm-config.xml
file using the<DeviceMonitorF
requency> tag.
"monitor_interval" : "$(monitoring_frequency)"
...
Going into production
When going into production, it is not recommended to use the H2 database. The following are instructions on how to configure MySQL databases:
- Install MySQL.
sudo apt-get install mysql-server mysql-client
- Set the MySQL root password.
- Start the MySQL service.
sudo /etc/init.d/mysql start
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.
Create the
WSO2_EMM_DB
as follows:In the MySQL prompt, create the database.
create database WSO2_EMM_DB;
Give authorization for the database to the admin user as follows. Thereafter, exit the MySQL Console.
GRANT ALL ON WSO2_EMM_DB.* TO admin@localhost IDENTIFIED BY "<MYSQL ADMIN PASSWORD>";
Run the MySQL scripts as follows:
mysql -u admin -p -DWSO2_EMM_DB < <PRODUCT_HOME>/dbscripts/emm/mysql.sql;
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.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.Code Block <datasource> <name>WSO2_EMM_DB</name> <description>The datasource used for EMM</description> <jndiConfig> <name>jdbc/WSO2EMMDB</name> </jndiConfig> <definition type="RDBMS"> <configuration> <url>jdbc:mysql://localhost:3306/WSO2EMM_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>
Create the
WSO2_CARBON_DB
as follows:In the MySQL prompt, create the database.
create database WSO2_CARBON_DB;
Give authorization for the database to the admin user as follows. Thereafter, exit the MySQL Console.
Info As the user named admin was created in step 5, we do not need to create a user again in this step.
GRANT ALL ON WSO2_CARBON_DB.* TO admin@localhost;
Run the MySQL scripts as follows:
mysql -u admin -p -DWSO2_CARBON_DB < <PRODUCT_HOME>/dbscripts/mysql.sql;
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.Code Block <datasource> <name>WSO2_CARBON_DB</name> <description>The datasource used for registry and user manager</description> <jndiConfig> <name>jdbc/WSO2CarbonDB</name> </jndiConfig> <definition type="RDBMS"> <configuration> <url>jdbc:mysql://localhost:3306/WSO2_CARBON_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>
Create the
WSO2AM_DB
as follows:In the MySQL prompt, create the database.
create database WSO2AM_DB;
Give authorization for the database to the admin user as follows. Thereafter, exit the MySQL Console.
Info As the user named admin was created in step 5, we do not need to create a user again in this step.
GRANT ALL ON WSO2AM_DB.* TO admin@localhost;
Run the MySQL scripts as follows:
mysql -u admin -p -DWSO2AM_DB < <PRODUCT_HOME>/dbscripts/apimgt/mysql.sql;
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.Code Block <datasource> <name>WSO2AM_DB</name> <description>The datasource used for API manager database</description> <jndiConfig> <name>jdbc/WSO2AM_DB</name> </jndiConfig> <definition type="RDBMS"> <configuration> <defaultAutoCommit>false</defaultAutoCommit> <url>jdbc:mysql://localhost:3306/WSO2AM_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>
Create tenants and test WSO2 EMM throughly. Once the tests are run successfully, it is safe to consider that the upgrade is ready for production. However, it is advised to test any features that are being used in production.