How jmeter scripts be executed over specific time period.

Think that you need to execute performance test for 1 hour.

Steps:

One possible way is use “Scheduler” in thread group.

Once you tick on “scheduler”, start time and end time can be given.

For example:

Start time: 2014/02/20 09:00:00

End Time: 2014/02/20 10:00:00

However, using scheduler is a overhead when you have to repeat the test several times, it should be edited again and again.

There is another way to execute jmeter scripts over particular time period by overcoming modification overhead.

Use "Ultimate thread group".

For that use have to download additional plug-in called “JMeterPlugins-Standard-1.1.3” and place it in lib/ext folder.

1. Download stnadard plu-in (JMeterPlugins-Standard-1.1.3.zip) from http://jmeter-plugins.org/downloads/all/
2. Unzip the downloaded file
3. Navigate to lib/ext and copy “JmeterPlugins-Standard.jar” and place it on jmeter distribution lib/ext folder
4. restart jmeter if it already started.
5. On the jmeter UI, now you can add “ultimate thread group”
6. Click on “Add Row”

Now you can define how long the test should be executed by using the “Hold Load for, sec” option.

For one hour test explained above you can use the below settings:

Note: No need to modify this script over and over again when you want to run it for several times. 

View Jmeter summary in non-GUI mode

I recently had to execute jmeter scripts on non GUI mode and wanted to view results while the test is executing.

Usually, on UI mode we can view the summary from “Summary Report” option.

But, when the test is executing through non GUI mode, usually we can not view the result rather waiting until the results written to particular file.

Below example shows how the jmeter scripts execute on non GUI mode.

 ./bin/jmeter.sh -n -t ~/jmeter/scripts/test1.jmx -l ~/jmeter/results/results1.jtl  

Note: test1.jmx file is the jmeter test plan. Result1.jtl is the result file generated.

When the test execution happening over long time and we need to view results during that period. For that we can use “Summariser” option.

Summariser is a special listener that only applies to non GUI mode. 

This option is provided in jmeter.properties file. (Actually $jmeter_home/bin).

jmeter.propertie contains special section for summariser options

 #---------------------------------------------------------------------------  
 # Summariser - Generate Summary Results - configuration (mainly applies to non-GUI mode)  
 #---------------------------------------------------------------------------  
 #  
 # Define the following property to automatically start a summariser with that name  
 # (applies to non-GUI mode only)  
 #summariser.name=summary  
 #  
 # interval between summaries (in seconds) default 3 minutes  
 #summariser.interval=180  
 #  
 # Write messages to log file  
 #summariser.log=true  
 #  
 # Write messages to System.out  
 #summariser.out=true  

What you need to do is uncomment the 4 options.

summariser.name=summary

summariser.interval=180 : Here you can define any time interval to display the results.

summariser.log=true

summariser.out=true

Now execute the same command and see the summary during test execution.

 ./bin/jmeter.sh -n -t ~/jmeter/scripts/test1.jmx -l ~/jmeter/results/results1.jtl  

Summary will be printed on the jmeter console:

 Creating summariser <summary>  
 Created the tree successfully using /home/ubuntu/jmeter/scripts/test1 .jmx  
 Starting the test @ Thu Feb 20 10:25:14 UTC 2014 (1392891914636)  
 Waiting for possible shutdown message on port 4445  
 summary + 99960 in  104s = 961.9/s Avg:  26 Min:   3 Max:  806 Err:   0 (0.00%) Active: 30 Started: 30 Finished: 0  
 summary + 306897 in  180s = 1704.5/s Avg:  17 Min:   3 Max:  297 Err:   0 (0.00%) Active: 30 Started: 30 Finished: 0  
 summary = 406857 in  284s = 1433.0/s Avg:  19 Min:   3 Max:  806 Err:   0 (0.00%)  
 summary + 298083 in  180s = 1655.7/s Avg:  17 Min:   3 Max:  322 Err:   0 (0.00%) Active: 30 Started: 30 Finished: 0  
 summary = 704940 in  464s = 1519.5/s Avg:  18 Min:   3 Max:  806 Err:   0 (0.00%)  
 summary + 264542 in  155s = 1704.9/s Avg:  16 Min:   3 Max:  304 Err:   0 (0.00%) Active: 0 Started: 30 Finished: 30  
 summary = 969482 in  619s = 1566.2/s Avg:  18 Min:   3 Max:  806 Err:   0 (0.00%)  
 Tidying up ...  @ Thu Feb 20 10:35:35 UTC 2014 (1392892535107)  

The main advantage of this is you can see what is happening during long running test. 

WSO2 ESB becomes fastest ESB in the space

It is very exited to see WSO2 ESB becomes world fastest ESB. This has been clearly proved by recent analysis of performance round: WSO2ESB Performance Round 7.5”. It has compared with WSO2 ESB newest release: ESB 4.8.1 and other leading open source ESBs.

Summary of the result as follows:

XML to JSON conversion when multiple attributes and elements exists

There are situations that we need to convert xml payloads into JSON. WSO2 ESB provides this support and refer http://docs.wso2.org/display/ESB481/JSON+Support for more details.

To convert an XML payload into JSON, we have to set the messageType property to application/json in synapse configuration.

Here I discuss about XML to JSON conversion when multiple attributes and elements available in the payload.

You may receive a soap request as follows:

SOAP Request:

 <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:m0="http://services.samples" xmlns:xsd="http://services.samples/xsd">  
 <soapenv:Header/>  
 <soapenv:Body>  
 <m0:getQuote xmlns:m0="http://services.samples" id="12345">  
 <person sex="female" fn:target="urn:getQuote" xmlns:fn="abcdef" id="12345">  
 <firstname>Anna</firstname>  
 <lastname id="12345678">Smith</lastname>  
 </person>  
 <m0:request>  
 <m0:symbol>A</m0:symbol>  
 </m0:request>  
 </m0:getQuote>  
 </soapenv:Body>  
 </soapenv:Envelope>   

Person element contains multiple attributes sex, target, namespace and id.

i.e:  <person sex="female" fn:target="urn:getQuote" xmlns:fn="abcdef" id="12345">  

Also, lastnname is a sub element of person and it contains attribute as id and text content as "Smith"

i.e: <lastname id="12345678">Smith</lastname>

We will see how to covert such payload into json and its how the response looks like.

In ESB create a proxy service with SimpleStockQuote endpoint.

Proxy Service Configuration:

 <?xml version="1.0" encoding="UTF-8"?>  
 <proxy xmlns="http://ws.apache.org/ns/synapse"  
 name="XMLtoJSON"  
 transports="https,http"  
 statistics="disable"  
 trace="disable"  
 startOnLoad="true">  
 <target>  
 <inSequence>  
 <property name="messageType" value="application/json" scope="axis2"/>  
 <log level="full"/>  
 <respond/>  
 </inSequence>  
 <outSequence>  
 <send/>  
 </outSequence>  
 <endpoint>  
 <address uri="http://localhost:9000/services/SimpleStockQuoteService/"/>  
 </endpoint>  
 </target>  
 <description/>  
 </proxy>   

Note: 
For conversion, use "<property name="messageType" value="application/json" scope="axis2"/>" in the configuration as discussed above.

1. You have to start sample backend to receove response which is provided with WSO2 ESB. (Start axis2Service @ESB_HOME/samples/axis2Server)

2. Built SimpleStockQuote Service @ESB_HOME/samples/axis2Server/src/SimpleStockQuoteService by running "ant" command.

3. Send the SOAP request to proxy service using SOAP UI.

Response should be as follows:

 HTTP/1.1 200 OK  
 Host: shashi-ThinkPad-T530:8280  
 SOAPAction: "urn:getQuote"  
 Accept-Encoding: gzip,deflate  
 Content-Type: application/json  
 Date: Fri, 24 Jan 2014 06:00:54 GMT  
 Server: WSO2-PassThrough-HTTP  
 Transfer-Encoding: chunked  
 Connection: Keep-Alive  
 {"getQuote":{"@id":"12345","person":{"@id":"12345","@sex":"female","@target":"urn:getQuote","firstname":"Anna","lastname":{"@id":"12345678","$":"Smith"}},"request":{"symbol":"A"}}}  

Points to focus in response:

1. Content-Type should be 'application/json'

2. XML: 

<person sex="female" fn:target="urn:getQuote" xmlns:fn="abcdef" id="12345">  

JSON:

"person":{"@id":"12345","@sex":"female","@target":"urn:getQuote"

*** Attributes displayed with prefix '@' in JSON conversion. ("@id":"12345")

When nodes has text content as well as attributes, that text content is stored in a key with “$”

XML:

 <lastname id="12345678">Smith</lastname>  

JSON:

"lastname":{"@id":"12345678","$":"Smith"}

If a node has multiple children with the same tag name, they are converted into a numerically indexed array e.g. “person”
XML

 <person>Anvar</person>  
 <person>Porter</person>  
 <person>Raj</person>  

JSON

"person":["Anvar","Porter","Raj"]

SOAP request:

 <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:m0="http://services.samples" xmlns:xsd="http://services.samples/xsd">  
 <soapenv:Header/>  
 <soapenv:Body>  
 <m0:getQuote xmlns:m0="http://services.samples" id="12345">  
 <person>Anvar</person>  
 <person>Porter</person>  
 <person>Raj</person>  
 <m0:request>  
 <m0:symbol>A</m0:symbol>  
 </m0:request>  
 </m0:getQuote>  
 </soapenv:Body>  
 </soapenv:Envelope>  

Response:

 HTTP/1.1 200 OK  
 Host: shashi-ThinkPad-T530:8280  
 SOAPAction: "urn:mediate"  
 Accept-Encoding: gzip,deflate  
 Content-Type: application/json  
 Date: Sun, 09 Feb 2014 02:49:07 GMT  
 Server: WSO2-PassThrough-HTTP  
 Transfer-Encoding: chunked  
 Connection: Keep-Alive  
 {"getQuote":{"@id":"12345","person":["Anvar","Porter","Raj"],"request":{"symbol":"A"}}}  

Working with WSO2 ESB Tasks with 'injectTo' property

WSO2 ESB Tasks allows to run scheduled jobs at specified intervals which is triggered by a timer. In this blog post I discuss about how to use 'injectTo' property with tasks.

Injecting the message to a proxy service:

Basic structure as follows:

<property xmlns:task="http://www.wso2.org/products/wso2commons/tasks"

name="injectTo"

value="proxy"/>

….......................

<property xmlns:task="http://www.wso2.org/products/wso2commons/tasks"

name="proxyName"

value="SampleProxy"/>

1. Use the configuration below
2. Start inbuilt backend service 'axis2serever' at $ESB_HOME/samples/axis2Server
3. Here I use SimplestockQuoteService and you need to built it by running ant command at $ESB_HOME/samples/axis2Server/src/SimpleStockQuoteService
4. Retart ESB and see task triggered 2 times withing 5ms as per below example:
   <trigger count="2" interval="5"/> 

 <?xml version="1.0" encoding="UTF-8"?>  
 <definitions xmlns="http://ws.apache.org/ns/synapse">  
   <registry provider="org.wso2.carbon.mediation.registry.WSO2Registry">  
    <parameter name="cachableDuration">15000</parameter>  
   </registry>  
   <proxy name="SampleProxy"  
      transports="https http"  
      startOnLoad="true"  
      trace="disable">  
    <description/>  
    <target endpoint="A">  
      <inSequence>  
       <log>  
         <property name="LOG"  
              value="======================================================="/>  
       </log>  
      </inSequence>  
      <outSequence>  
       <log>  
         <property name="LOG" value="******************************************"/>  
       </log>  
      </outSequence>  
    </target>  
   </proxy>  
   <endpoint name="A">  
    <address uri="http://localhost:9000/services/SimpleStockQuoteService"/>  
   </endpoint>  
   <sequence name="fault">  
    <log level="full">  
      <property name="MESSAGE" value="Executing default 'fault' sequence"/>  
      <property name="ERROR_CODE" expression="get-property('ERROR_CODE')"/>  
      <property name="ERROR_MESSAGE" expression="get-property('ERROR_MESSAGE')"/>  
    </log>  
    <drop/>  
   </sequence>  
   <sequence name="main">  
    <in>  
      <log level="full"/>  
      <filter source="get-property('To')" regex="http://localhost:9000.*">  
       <send/>  
      </filter>  
    </in>  
    <out>  
      <send/>  
    </out>  
    <description>The main sequence for the message mediation</description>  
   </sequence>  
   <task name="SampleInjectToSequenceTask"  
      class="org.apache.synapse.startup.tasks.MessageInjector"  
      group="synapse.simple.quartz">  
    <trigger count="2" interval="5"/>  
    <property xmlns:task="http://www.wso2.org/products/wso2commons/tasks" name="message">  
      <m0:getQuote xmlns:m0="http://services.samples">  
       <m0:request>  
         <m0:symbol>IBM</m0:symbol>  
       </m0:request>  
      </m0:getQuote>  
    </property>  
    <property xmlns:task="http://www.wso2.org/products/wso2commons/tasks"  
         name="proxyName"  
         value="SampleProxy"/>  
    <property xmlns:task="http://www.wso2.org/products/wso2commons/tasks"  
         name="injectTo"  
         value="proxy"/>  
   </task>  
 </definitions>  

Injecting the message to a proxy service:

Basic structure as follows:

<property xmlns:task="http://www.wso2.org/products/wso2commons/tasks"

name="injectTo"

value="sequence"/>

….......................

<property xmlns:task="http://www.wso2.org/products/wso2commons/tasks"

name="sequenceName"

value="SampleSequence"/>

1. Use the configuration below.
2. Same axis2service and SimpleStokQuote service can be used as per above
3. Retart ESB and see task triggered 3 times withing 10ms as per below example:
   <trigger count="3" interval="10"/>

 <?xml version="1.0" encoding="UTF-8"?>  
 <definitions xmlns="http://ws.apache.org/ns/synapse">  
   <registry provider="org.wso2.carbon.mediation.registry.WSO2Registry">  
    <parameter name="cachableDuration">15000</parameter>  
   </registry>  
   <proxy name="SampleProxy"  
      transports="https http"  
      startOnLoad="true"  
      trace="disable">  
    <description/>  
    <target endpoint="A">  
      <inSequence>  
       <log>  
         <property name="LOG"  
              value="======================================================="/>  
       </log>  
      </inSequence>  
      <outSequence>  
       <log>  
         <property name="LOG" value="******************************************"/>  
       </log>  
      </outSequence>  
    </target>  
   </proxy>  
   <endpoint name="A">  
    <address uri="http://localhost:9000/services/SimpleStockQuoteService"/>  
   </endpoint>  
   <sequence name="fault">  
    <log level="full">  
      <property name="MESSAGE" value="Executing default 'fault' sequence"/>  
      <property name="ERROR_CODE" expression="get-property('ERROR_CODE')"/>  
      <property name="ERROR_MESSAGE" expression="get-property('ERROR_MESSAGE')"/>  
    </log>  
    <drop/>  
   </sequence>  
   <sequence name="recSeq">  
    <log level="full">  
      <property name="MSG" value="===== RESPONSE ====="/>  
    </log>  
    <drop/>  
   </sequence>  
   <sequence name="SampleSequence">  
    <send receive="recSeq">  
      <endpoint>  
       <address uri="http://localhost:9000/services/SimpleStockQuoteService"/>  
      </endpoint>  
    </send>  
   </sequence>  
   <sequence name="main">  
    <in>  
      <log level="full"/>  
      <filter source="get-property('To')" regex="http://localhost:9000.*">  
       <send/>  
      </filter>  
    </in>  
    <out>  
      <send/>  
    </out>  
    <description>The main sequence for the message mediation</description>  
   </sequence>  
   <task name="SampleInjectToSequenceTask"  
      class="org.apache.synapse.startup.tasks.MessageInjector"  
      group="synapse.simple.quartz">  
    <trigger count="3" interval="10"/>  
    <property xmlns:task="http://www.wso2.org/products/wso2commons/tasks"  
         name="injectTo"  
         value="sequence"/>  
    <property xmlns:task="http://www.wso2.org/products/wso2commons/tasks" name="message">  
      <m0:getQuote xmlns:m0="http://services.samples">  
       <m0:request>  
         <m0:symbol>IBM</m0:symbol>  
       </m0:request>  
      </m0:getQuote>  
    </property>  
    <property xmlns:task="http://www.wso2.org/products/wso2commons/tasks"  
         name="sequenceName"  
         value="SampleSequence"/>  
   </task>  
 </definitions>  

SAML2.0 Assertion with WSO2 Identity Server

In this blog post I will discuss the steps for “Creating SAML2.0 Bearer Assertion profile for OAuth 2.0 with WSO2 Identity Server”.

1. Download latest IS release from http://wso2.com/products/identity-server/.
   (Here I use WSO2 IS 4.6.0 since it is the latest release at the time of writing this blog post.)
   
2. Create a SAML2 Assertion. You can use the command line client program (SAML2AssertionCreator) from here. Extract the ZIP file and navigate to the lib folder and execute the following command in the command linejava -jar SAML2AssertionCreator.jar <issuer> <username> <recipient> <requestedAudiences> <keyStoreFile> <keyStorePassword> <alias> <privateKeyPassword> <comma seperated user calimvalue pairs(claim:value)>
   ex:
   java -jar SAML2AssertionCreator.jar SAML2AssertionCreator shashika https://localhost:9443/oauth2/token https://localhost:9443/oauth2/token /home/shashika/Downloads/saml-oauth/wso2is-4.6.0/repository/resources/security/wso2carbon.jks wso2carbon wso2carbon wso2carbon FirstName|shashika,LastName|Ubhayaratne,Country|SriLanka

Note the “base64-url Encoded Assertion String” from the reply above and copy the part “PD.......3D”. This needs to be used in step 5.

3. Register new Trusted Identity Provider.
   

• Go to Configure -> Trusted Identity Providers.
  
• Click on ‘Add New Trusted Identity Provider’.
  
• Enter a unique identifier for this Trusted Identity Provider across the tenant.
  

ex :

• Identity Provider Name: sampleidp
  
• Identity Provider Issuer: SAML2AssertionCreator
  
• Identity Provider Public Certificate: << attach the certificate “wso2pem.pem” >> (You can generate this public certificate using kytool: (keytool -export -alias wso2cert -file wso2pem.pem -keystore wso2carbon.jks)
  
• Identity Provider Audience: https://localhost:9443/oauth2/token
  

4. Create a new OAuth2.0 application under Main -> Manage -> OAuth
   SAML should be selected as “Allowed Grant Types”.
   
5. Execute the following HTTP request to the https://localhost:9443/oauth2/token endpointcurl -X POST -k -u "<Client Id>:<Client Secret>" -H "Content-Type: application/x-www-form-urlencoded;charset=UTF-8" -d "grant_type=urn:ietf:params:oauth:grant-type:saml2-bearer&scope=openid&assertion=<base64-url Encoded Assertion from step 2>" https://localhost:9443/oauth2/token/
   curl -X POST -k -u "noEnn5tvU5tgEJfHImicSApBMAwa:RMauKZY7H1GAWFJ77vffMI8Pv9ka" -H "Content-Type: application/x-www-form-urlencoded;charset=UTF-8" -d "grant_type=urn:ietf:params:oauth:grant-type:saml2-bearer&scope=openid&assertion=PD94bWwg<<.....>>9uPg%3D%3D" https://localhost:9443/oauth2/token/
   Note: assertion=PD94bWwg<<.....>>9uPg%3D%3D. This should be taken from Step2.
   
6. In the response from above step you will get the base64 encoded id token
   ex: {"token_type":"bearer","expires_in":481,"refresh_token":"71df5c5a5ca2b6dc84c2cf2d64183342","id_token":"eyJhbGciOiJub25lIiwidHlwIjoiSldUIn0=\r\n.eyJleHAiOi0zNzcyNjI5NywiYXpwIjoiZklFa1p0aW5yYnBMQlh4WDgzbXdEekNQOEFBYSIsInN1\r\nYiI6ImlzaGFyYSIsImF1ZCI6ImZJRWtadGlucmJwTEJYeFg4M213RHpDUDhBQWEiLCJpc3MiOiJo\r\ndHRwczpcL1wvbG9jYWxob3N0Ojk0NDNcL29hdXRoMmVuZHBvaW50c1wvdG9rZW4iLCJGaXJzdE5h\r\nbWUiOiJJc2hhcmEiLCJMYXN0TmFtZSI6IkthcnVuYXJhdGhuYSIsIkNvdW50cnkiOiJTcmlMYW5r\r\nYSIsImlhdCI6LTQxMzI2Mjk3fQ==\r\n.","access_token":"466d19d052acd21aec3ce045cb46329b"}
   
7. Decoding the id_token value you can get the user claims. (Id token contains two values separated by '.')
   Refer bold part from the response, Remove “/r/n” parts and paste it on decoder.
   Go to “http://www.base64decode.org/”
   Paste the copied text here.
   Text should be prepared as follows: eyJleHAiOi0zNzcyNjI5NywiYXpwIjoiZklFa1p0aW5yYnBMQlh4WDgzbXdEekNQOEFBYSIsInN1YiI6ImlzaGFyYSIsImF1ZCI6ImZJRWtadGlucmJwTEJYeFg4M213RHpDUDhBQWEiLCJpc3MiOiJo\r\ndHRwczpcL1wvbG9jYWxob3N0Ojk0NDNcL29hdXRoMmVuZHBvaW50c1wvdG9rZW4iLCJGaXJzdE5hbWUiOiJJc2hhcmEiLCJMYXN0TmFtZSI6IkthcnVuYXJhdGhuYSIsIkNvdW50cnkiOiJTcmlMYW5rYSIsImlhdCI6LTQxMzI2Mjk3fQ==
   Decoded String:
   {"exp":170653649,"azp":"noEnn5tvU5tgEJfHImicSApBMAwa","sub":"shashika","aud":"noEnn5tvU5tgEJfHImicSApBMAwa","iss":"https:\/\/localhost:9443\/oauth2endpoints\/token","FirstName":"shashika","LastName":"ubhayaratne","Country":"SriLanka","iat":167053649}
   

How to Start WSO2 ESB with external LDAP

How to Start WSO2 ESB with external LDAP

WSO2 ESB is a fast, light-weight, and versatile Enterprise Service Bus. Using WSO2 ESB you can perform a variety of enterprise integration patterns, including filtering, transforming, and routing SOAP, binary, plain XML, and text messages that pass through your business systems by HTTP, HTTPS, JMS, mail, etc.

For more information read: http://wso2.com/products/enterprise-service-bus/.

By default, ESB uses embedded jdbc user store as user management data source.

Default configuration as follows:

<UserStoreManager class="org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager">

<Property name="ReadOnly">false</Property>

<Property name="MaxUserNameListLength">100</Property>

<Property name="IsEmailUserName">false</Property>

<Property name="DomainCalculation">default</Property>

<Property name="PasswordDigest">SHA-256</Property>

<Property name="StoreSaltedPassword">true</Property>

<Property name="UserNameUniqueAcrossTenants">false</Property>

<Property name="PasswordJavaRegEx">^[\S]{5,30}$</Property>

<Property name="PasswordJavaScriptRegEx">^[\\S]{5,30}$</Property>

<Property name="UsernameJavaRegEx">^[^~!#$;%^*+={}\\|\\\\&lt;&gt;,\'\"]{3,30}$</Property>

<Property name="UsernameJavaScriptRegEx">^[\\S]{3,30}$</Property>

<Property name="RolenameJavaRegEx">^[^~!#$;%^*+={}\\|\\\\&lt;&gt;,\'\"]{3,30}$</Property>

<Property name="RolenameJavaScriptRegEx">^[\\S]{3,30}$</Property>

<Property name="UserRolesCacheEnabled">true</Property>

<Property name="maxFailedLoginAttempt">0</Property>

</UserStoreManager>

Now, I'll explain how to use external LDAP for ESB user-management user store.

WSO2 IS has its embedded LDAP and here I am going to use it as ESB's external LDAP.

Prerequisites: You need WSO2 ESB and WSO2 IS.

Download them form http://wso2.com/products/enterprise-service-bus/ and (http://wso2.com/products/identity-server)

Any version you can choose as per the requirement and extract them

Step 1: Start IS with default port.

Step 2: Change ESB offset (since WSO2 IS uses the default port as per Step 1)

1. Navigate to ESB_HOME/repository/conf/carbon.xml
   ex: <Offset>1</Offset>

Step 3: Chage user-mgt.xml (ESB_HOME/repository/user-mgt.xml

1. <Property name="MultiTenantRealmConfigBuilder">org.wso2.carbon.user.core.config.multitenancy.CommonLDAPRealmConfigBuilder</Property>
2. Comment default internal JDBC user store configurations ( showed in the beginning of this article)
3. Uncomment external LDAP section

<!-- If product is using an external LDAP as the user store in read/write mode, use following user manager

In case if user core cache domain is needed to identify uniquely set property <Property name="UserCoreCacheIdentifier">domain</Property> -->

<UserStoreManager class="org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager">

<Property name="ConnectionURL">ldap://localhost:10389</Property>

<Property name="ConnectionName">uid=admin,ou=system</Property>

<Property name="ConnectionPassword">secret</Property>

<Property name="passwordHashMethod">PLAIN_TEXT</Property>

<Property name="UserNameListFilter">(objectClass=person)</Property>

<Property name="UserEntryObjectClass">inetOrgPerson</Property>

<Property name="UserSearchBase">ou=system</Property>

<Property name="UserNameSearchFilter">(&amp;(objectClass=person)(uid=?))</Property>

<Property name="UserNameAttribute">uid</Property>

<Property name="UsernameJavaRegEx">[a-zA-Z0-9._-|//]{3,30}$</Property>

<Property name="UsernameJavaScriptRegEx">^[\\S]{3,30}$</Property>

<Property name="RolenameJavaScriptRegEx">^[\\S]{3,30}$</Property>

<Property name="RolenameJavaRegEx">[a-zA-Z0-9._-|//]{3,30}$</Property>

<Property name="PasswordJavaScriptRegEx">^[\\S]{5,30}$</Property>

<Property name="ReadLDAPGroups">true</Property>

<Property name="WriteLDAPGroups">true</Property>

<Property name="EmptyRolesAllowed">false</Property>

<Property name="GroupSearchBase">ou=system</Property>

<Property name="GroupNameListFilter">(objectClass=groupOfNames)</Property>

<Property name="GroupEntryObjectClass">groupOfNames</Property>

<Property name="GroupNameSearchFilter">(&amp;(objectClass=groupOfNames)(cn=?))</Property>

<Property name="GroupNameAttribute">cn</Property>

<Property name="MembershipAttribute">member</Property>

<Property name="UserRolesCacheEnabled">true</Property>

<Property name="ReplaceEscapeCharactersAtUserLogin">true</Property>

<Property name="maxFailedLoginAttempt">0</Property>

<Property name="DomainName">domain.com</Property>

</UserStoreManager>

4. You need to change some properties according to IS user-mgt.xml (Refer the IS user-mgt/xml and its default LDAP settings)

• No need to change the LDAP Port if IS started on default port
  (Othereise: 10389+<offset value>)
  ie: <Property name="ConnectionURL">ldap://localhost:10389</Property>
• <Property name="ConnectionPassword">admin</Property>
• <Property name="passwordHashMethod">SHA</Property>
• <Property name="UserEntryObjectClass">identityPerson</Property>
• <Property name="UserSearchBase">ou=Users,dc=wso2,dc=org</Property>
• <Property name="GroupSearchBase">ou=Groups,dc=wso2,dc=org</Property>

Step 4: Start ESB