How to configure WSO2 G-Reg with ELB - Updated

This is the updated post for configuring WSO2 ELB 2.1.0 and G-Reg 4.6.0 releases. If you are using earlier releases, please refer the early post.

 When we are fronting WSO2 ELB(Elastic Load Balancer) for a WSO2 G-Reg(Governance Registry) node, all the incoming messages will go through ELB node and it will act as a HTTP and HTTPS proxy to GREG node. So when you configure ELB to the GREG front, GREG won't be able to access alone without the ELB.

1. Download WSO2 ELB and WSO2 GREG. Rename the extracted ELB as ELB-HOME and extracted GREG as GREG-HOME.

ELB Configuration 

2. Go to ELB-HOME/repository/conf/loadbalancer.conf and add the following entry. There can be multiple entries according to the clustering requirements.

 governance {

  domains   {

           wso2.governance.domain {

               tenant_range *;
               group_mgt_port 4000;
               mgt{
                   hosts governance.local.wso2.com;
               }
           }
       }
}
 3. Update hosts files in nodes with relevant IP and Domain information. In my example, G-Reg and ELB will be hosted on the same node.

127.0.0.1 governance.local.wso2.com 
if not this governance.local.wso2.com domain should be mapped into ELB node.

 4 Navigate to the repository/conf/axis2 directory and open the axis2.xml file and update localMemberPort parameter value as below. This port number should not conflict with any other port.

<parameter name="localMemberPort">5000</parameter>

Greg Configuration



4. Then clustering should be enabled in G-Reg as well. To enable it, go to GREG-HOME/repository/conf/axis2/axis2.xml and modify clustering configuration as below.






<clustering class="org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent" enable="true">
 <parameter name="membershipScheme">wka </parameter> 
</clustering>




 5. Uncomment localmemberhost element in GREG-HOME/repository/conf/axis2/axis2.xml and specify the IP address (or host name) to be exposed to members of the cluster.




<parameter name="localMemberHost">127.0.0.1</parameter>





6. Then define clustering domain information.(in GREG-HOME/repository/conf/axis2/axis2.xml). This "domain" name value should be same as in loadbalancer.conf. 






<parameter name="domain">wso2.governance.domain</parameter>
<parameter name="localMemberPort">4250</parameter>



7. As shown below, add "subDomain" information into the same axis2.xml file. 






<parameter name="properties">
    <property name="backendServerURL" value="https://${hostName}:${httpsPort}/services/"/>
    <property name="mgtConsoleURL" value="https://${hostName}:${httpsPort}/"/>
    <property name="subDomain" value="mgt"/>
   </parameter>




8. Add load balancer IP address or host information in to same axis2.xml file. In this example scenario IP address is 127.0.0.1. 







<members>
     <member>
        <hostname>127.0.0.1 </hostname>
        <port>4000</port>
     </member>
  </members>
</members>




9. Open the GREG-HOME/repository/conf/tomcat/catalina-server.xml file and add HTTP and HTTPS proxy port information to that file. 






<connector port="9763" protocol="org.apache.coyote.http11.Http11NioProtocol" proxyport="8280"/> 
<connector port="9443" protocol="org.apache.coyote.http11.Http11NioProtocol" proxyport="8243"/>






10. Go to GREG-HOME/repository/conf/carbon.xml file and update the "HostName" and "MgtHostName" as below. 






<hostname>governance.local.wso2.com</hostname>
<mgthostname>governance.local.wso2.com</mgthostname>




11. This step only need to be followed if you are hosting G-Reg and ELB both in same node. In this sample we have configured both ELB and G-Reg in same node. Therefore we should avoid port conflicts between ELB and G-Reg. To avoid such problems we can use "Offset" entry in carbon.xml file. Go to GREG-HOME/repository/conf/carbon.xml and change port offset value. 






<offset>1</offset>



12. Start the ELB instance



13. Start the G-Reg instance(s)



14.You can access G-Reg instance using following URL         "https://governance.local.wso2.com:8243/carbon/"











































Comments








Post a Comment























Popular posts from this blog









XSLT - Modify Date and DateTime value





















If you want to perform date and time related opertions with XSLT 'date' or 'dateTime' values, you can use 'xs:yearMonthDuration' or 'xs:dayTimeDuration' function to achieve this. You can add or reduce years, months, date, hours or even minutes through those functions.     xs:yearMonthDuration   For this function input value is year month duration and it should be passed in  ISO_8601 format    n- the [n] is replaced by the value for each of the date and time elements  P - The duration designator(for period).    nY- the number of years.   nM- the number of months.    ex: xs:yearMonthDuration('P1Y2M')  - 1 Year and 2 Months   ex:  xs:yearMonthDuration('-P1Y2M')  - Negative 1 Year and 2 Months   xs:dayTimeDuration   For this function input value is day time duration and it also needs to be passed in  ISO_8601 format   n- the [n] is replaced by the value for each of the date and time elements  P - The duration designator(for period).   nD- the








Read more










Integrate With Mutual Certificate Authentication based Service





















There are many ways to secure a Service/API using different Authentication mechanisms. Mutual Certificate authentication(AKA: Client Certificate Authentication) is one of the ways to secure Service or API. Recently I was trying to integrate with an API which is secured using Mutual Certificate Authentication. In this scenario, the backend service team gave me their certificate-based on PKCS#12. When integrating this backend system with WSO2 Platform, we have to use 'Multi-HTTPS transport'. With this 'Multi-HTTPS transport', it will grant great flexibility to define different SSL profiles with separate trust stores and key stores for different IPs or hosts. This custom SSL profile can be implemented for Client to Synapse Runtime(Client --> ESB) or Synapse Runtime to Backend(ESB --> Backend). If it is Client to ESB, then you have to define custom SSL Profiles in the transportReceiver section. In my use-case, it was for ESB to Backend. So I had to add custom SSL prof








Read more










Yield Price Sri Lanka - Android Application




















Image







 " Yield Price Sri Lanka " is an Android based application which helps users to check Market Price Information using their mobile devices. This application concept is based on person X( will update his name after approvals) and I did slight modifications on the application to support in a low cost infrastructure.   Using this " Yield Price Sri Lanka " application, you can check prices of various goods instantly, without going to the market. I am updating price information in Daily & Weekly basis according to the Colombo Manning Market prices.   Initial application was developed to support English language only. With current latest version we are supporting English, Tamil and Sinhalese languages.   This application will update price information in real time and when describing the application's back-end(server) architecture, it has developed to serve JSON based output with many concurrent requests without blocking any request. Within the mobile Application wh








Read more