Configuring WSO2 EMM with Port Offset

There are situations when the default port needs to be changed in WSO2 EMM by using a port offset (e.g., when configuring WSO2 EMM with WSO2 App Manager). When the port offset is set WSO2 EMM will start on a different port, and it will change the default TCP port by increasing the value of the set port by the port offset value. Therefore, the port in the TCP connection URL that corresponds to the various the EMM related configuration files should be changed to enable WOS2 EMM to function properly.

More on port offset

The port offset feature allows you to run multiple WSO2 products, multiple instances of a WSO2 product, or multiple WSO2 product clusters on the same server or virtual machine (VM). The port offset defines the number by which all ports defined in the runtime such as the HTTP/S ports will be offset. For example, if the HTTP port is defined as 9763 and the portOffset is 1, the effective HTTP port will be 9764. Therefore, for each additional WSO2 product, instance, or cluster you add to a server, set the port offset to a unique value (the default is 0).

Follow the instructions below to enable port offset in EMM:

Change the default port that WSO2 EMM uses.
Define the port offset in the ports section of the carbon.xml file, which is in the <EMM_HOME>/repository/conf directory as follows:
```
<Offset>[PORT_OFFSET_VALUE]</Offset>
```
For example, if the port offset is 3, it can be defined as follows:
```
<Offset>3</Offset>
```
Define the updated port in the EMM configuration files.
Update the following configuration files with the relevant port details to reflect the port offset.

- Update the port in the following section that is within the cdm-config.xml file, which is in the <EMM_HOME>/repository/conf directory.
```
<ServerUrl>https://localhost:9443</ServerUrl>
```
- Update the port in the following section that is within the config.json file, which is in the <EMM_HOME>/repository/deployment/server/jaggeryapps/emm/app/conf directory. You are required to configure this file as it is used to manage the enrolled devices.
  
  Make sure that the URL mentioned under the host property is an HTTPS URL.
  Why is this needed?
  
  In WSO2 EMM, only Android and iOS platforms use the agent to enroll devices with the EMM. The Windows platform uses the native workplace application to enroll devices with WSO2 EMM. Therefore, the following configuration step is required only if you are registering or enrolling Android or iOS devices.
```
"generalConfig" : {
        "host" : "10.10.10.248:9443",
        "companyName" : "WSO2 Carbon Device Manager",
        "browserTitle" : "WSO2 Device Manager",
        "copyrightPrefix" : "\u00A9 %date-year%, ",
        "copyrightOwner" : "WSO2 Inc.",
        "copyrightOwnersSite" : "http://www.wso2.org",
        "copyrightSuffix" : " All Rights Reserved."
}
```
- Update the port in the following section that is within the config.json file, which is in the <EMM_HOME>/repository/deployment/server/jaggeryapps/emm-web-agent/app/conf directory. You are required to configure this file as it is used to handle device enrollments.
  
  Make sure that the following URL is HTTP, because the Android browser does not trust hosts with self-signed certificates. However, if your server has a valid SSL certificate installed, make the following URL HTTPS.
  Why is this needed?
  
  In WSO2 EMM, only Android and iOS platforms use the agent to enroll devices with the EMM. The Windows platform uses the native workplace application to enroll devices with WSO2 EMM. Therefore, the following configurations steps are required only if you are registering or enrolling Android or iOS devices.
```
"generalConfig" : {
        "host" : "http://10.10.10.45:9763",
        "companyName" : "WSO2 Enterprise Mobility Manager",
        "browserTitle" : "WSO2 EMM",
        "copyrightText" : "\u00A9 %date-year%, WSO2 Inc. (http://www.wso2.org) All Rights Reserved."
    } 
```