Versions Compared

Old Version 10

changes.mady.by.user Former user

Saved on

compared with

New Version 11

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Set up the cluster configurations by editing the <PRODUCT_HOME>/repository/conf/axis2/axis2.xml file as follows.
    1. Enable clustering for this node by setting enable to true in the clustering tag.
      <clustering class="org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent" enable="true">
    2. Set the membership scheme to wka to enable the well-known address registration method (this node sends cluster initiation messages to WKA members that are defined later).
      <parameter name="membershipScheme">wka</parameter>
    3. Specify the name of the cluster this node will join.
      <parameter name="domain">wso2.emm.domain</parameter>

    4. Specify the host used to communicate cluster messages.

      Note

      Note: You may run into issues when using host names in products based on WSO2 Carbon 4.4.0, so it is recommended that you use the IP address directly here. You can also use IP address ranges here. For example, 192.168.1.2-10.

      <parameter name="localMemberHost">xxx.xxx.xxx.xx3</parameter>

    5. Specify the port used to communicate cluster messages.
      <parameter name="localMemberPort">4200</parameter>

    6. Specify the well known member. In this example, the well known member is the manager node.

      Code Block
      languagexml
      <members>
	<member>
		<hostName>xxx.xxx.xxx.xx2</hostName>
		<port>4100</port> 
	</member>
</members>
  2. Configure the HostName. To do this, edit the <PRODUCT_HOME>/repository/conf/carbon.xml file to modify the following entry.
    <HostName>work.emm.wso2.com</HostName>

  3. Configure the HTTP/HTTPS proxy ports to communicate through the load balancer by editing the <PRODUCT_HOME>/repository/conf/tomcat/catalina-server.xml file as follows.

    Code Block
    languagexml
    <Connector protocol="org.apache.coyote.http11.Http11NioProtocol"
port="9763"
proxyPort="80"
redirectPort="443"
…
/>
<Connector protocol="org.apache.coyote.http11.Http11NioProtocol"
port="9443"
proxyPort="443"
redirectPort="443"
…
/>

  4. Stop running the monitoring task on worker nodes by editing the <PRODUCT_HOME>/repository/conf/cdm-config.xml and setting the monitoringEnable tag to false.

    Note

    Note: This task is not federated yet. Federation will be applicable in an upcoming release.

    <MonitoringEnable>false</MonitoringEnable>

  5. Configure the identity provider URL for OAuth key validation. Do this by editing the <PRODUCT_HOME>/repository/conf/security/authenticators.xml file.

    Code Block
    languagexml
    <Authenticator name="OAuthAuthenticator" disabled="false">
	<Priority>10</Priority>
	<Config>
		<Parameter name="isRemote">true</Parameter>
		<Parameter name="hostURL">https://keymgt.emm.wso2.com:443</Parameter>
		<Parameter name="adminUsername">admin</Parameter>
		<Parameter name="adminPassword">admin</Parameter>
	</Config>
</Authenticator>

  6. Change the apk download URL to the publically exposed URL in emm-web-agent jaggery application. This file is in emm-web-agent.zip file. You can unzip it, edit the file, and then zip it again. Edit the <PRODUCT_HOME>/repository/deployment/server/jaggeryapps/emm-web-agent/config/config.json file with the following.

    Code Block
    "generalConfig" : {
	"host" : "http://work.emm.wso2.com",
	"companyName" : "WSO2 Enterprise Mobility Manager",
	…………………….
}
  7. Remove the EMM jaggery application from the server before starting it. This is to make sure that no worker node has the ability to control the device through the EMM web application.

  8. Add the following to the tasks-config.xml file, which is in the <EMM_HOME>/repository/conf/etc/ directory in the Analyzer nodes.

    Code Block
    <taskServerCount>2</taskServerCount>
    Note
    titleAbout the task server count

    This value indicates the number of task servers running in the cluster.

    When clustering is enabled for worker nodes, they wait for other task executor nodes to startup. This depends on the number specified as the taskServerCount in the <EMM_HOME>/repository/conf/etc/tasks-config.xml file. 

    If the taskServerCount is 2 (which is the default value) then there should be at least two worker nodes to properly start up the cluster. Otherwise, the worker node startup will be held at the following log statement until at least one other task node startup.

Configuring the Key Manager node

...