How to import a server certificate to WSO2 key stores

Recently I was testing Nginx's load balancing capability with a WSO2 Application Server cluster which was consisted of one manager and two worker nodes fronted by an Nginx load balancer. I managed to successfully test the dep sync functionality by directly calling the manager/worker nodes of my cluster.

How ever when I tried to send HTTPS requests through the load balancer I encountered ssl certificate errors. Reason being the certificate setup for Nginx when setting up the cluster being not available inside our WSO2 key stores.

As a solution I imported the server.crt certificate file to WSO2 key stores and carry out my intended operations as expected without any certificate trouble. Here is how to do it.

1. Issue the following command which will give you basic certificate details and prompt a question. (It is assumed that both server.crt and wso2carbon.jks is in same folder; or else give the path accordingly)

> keytool -import -file server.crt -alias nginx -keystore wso2carbon.jks -storepass wso2carbon

Owner: EMAILADDRESS=sameera@wso2.com, CN=Sameera, OU=Carbon, O=WSO2, L=Colombo, ST=Western, C=SL
Issuer: EMAILADDRESS=sameera@wso2.com, CN=Sameera, OU=Carbon, O=WSO2, L=Colombo, ST=Western, C=SL
Serial number: 8b1edfc651beb3a3
Valid from: Tue Jun 16 19:40:22 IST 2015 until: Wed Jun 15 19:40:22 IST 2016
Certificate fingerprints:
  MD5:  1C:50:BB:9A:A1:01:49:D9:19:D2:BC:60:8F:6A:9A:11
  SHA1: 75:5D:B8:1B:F7:9F:05:46:BC:07:BA:C2:0E:7D:B1:B4:58:17:26:27
  SHA256: 17:C3:73:0E:D7:24:28:E5:FB:FE:A5:C4:C8:D9:A4:07:55:59:BA:55:37:1B:E8:14:12:64:7F:16:7A:A6:C3:C9
  Signature algorithm name: SHA256withRSA
  Version: 1

Question being asked is,

Trust this certificate? [no]:  yes

2. Type yes as shown above and press enter. You will get a response as follows.

Certificate was added to keystore

That's it. :)

> keytool -list -alias nginx -keystore client-truststore.jks -storepass wso2carbon -v
> keytool -list -alias nginx -keystore wso2carbon.jks -storepass wso2carbon -v

Sample output:

Alias name: nginx
Creation date: Aug 21, 2015
Entry type: trustedCertEntry

Owner: EMAILADDRESS=user@comp.com, CN=user, OU=Carbon, O=COMP, L=Colombo, ST=Western, C=SL
Issuer: EMAILADDRESS=user@comp.com, CN=user, OU=Carbon, O=COMP, L=Colombo, ST=Western, C=SL
Serial number: 8b1edfc651beb3a3
Valid from: Tue Jun 16 14:10:22 UTC 2015 until: Wed Jun 15 14:10:22 UTC 2016
Certificate fingerprints:
  MD5:  1C:50:BB:9A:A1:01:49:D9:19:D4:BC:60:8F:6A:9A:11
  SHA1: 75:5D:B8:1B:F7:9F:05:46:BC:27:BA:C2:0E:7D:B1:B4:58:17:26:27
  SHA256: 17:C3:73:0E:D7:24:28:E5:FB:FE:A5:C4:C4:D9:A4:07:55:59:BA:55:37:1B:E8:14:12:64:7F:16:7A:A6:C3:C9
  Signature algorithm name: SHA256withRSA
  Version: 1

HTTP load balancing with Nginx using simple HTTP python server instances

Introduction:
In this article we will be discussing how to perform HTTP load balancing with Nginx. For this purpose we will be using a simple HTTP python server. Three instances will be run on ports 8080, 8081 and 8082. Then by using cURL command (written in a shell script) we will be sending HTTP requests to the custom port.

Prerequisites:
1. Nginx installed on your OS.
You can find many articles in internet on how to install Nginx in your OS.

Content:
1. Configuring and starting Nginx
2. Starting three python HTTP server instances
3. Sending HTTP requests using cURL command embedded in a Shell script.
4. Monitoring output.
5. Stopping servers.
6. Errors

1. Configuring and starting Nginx
Goto your Nginx installation directory and find the nginx.conf configuration file.
e.g.: In my Mac OSX the path to nginx.conf is /usr/local/etc/nginx

In your nginx.conf file make sure the following line exists.

include servers/*;

This is because we are writing our custom configuration file inside the server directory.

You don't have to change the default port unless you get a conflict in starting Nginx.
If you are getting an Address already in use error please change your nginx.conf listen port as follows.
In http -> server section change the port according to your need.
e.g.: I have set it as listen 9980; since I got an Address already in use error at the beginning.

Now we are going to create the Nginx configuration file inside the server directory needed for our use case.
Go to servers directory inside your nginx installation directory, create a new file name localhost.conf.
servers/
└── localhost.conf

Paste the following content to it.

http {
        upstream localhost {
                server localhost:8080 ;
                server localhost:8081 ;
                server localhost:8082 ;
        }

        server {
                listen 8880;
                server_name localhost;
                location / {
                        proxy_pass http://localhost;
                }
        }

}

Now your Nginx configuration is complete.

Start Nginx server.

e.g.: Issue the following command

> nginx

Verify the Nginx Listening ports as follows.

Suhans-MacBook-Pro:nginx suhanr$ lsof -i TCP:9980 | grep LISTEN
nginx   96779 suhanr    6u  IPv4 0x4725c99a7ff095e9      0t0  TCP *:9980 (LISTEN)
nginx   96780 suhanr    6u  IPv4 0x4725c99a7ff095e9      0t0  TCP *:9980 (LISTEN)
Suhans-MacBook-Pro:nginx suhanr$ lsof -i TCP:8880 | grep LISTEN
nginx   96779 suhanr    8u  IPv4 0x4725c99a820272a9      0t0  TCP *:cddbp-alt (LISTEN)
nginx   96780 suhanr    8u  IPv4 0x4725c99a820272a9      0t0  TCP *:cddbp-alt (LISTEN)

If you have not used the default listening port in nginx.conf configuration skip lsof -i TCP:9980 | grep LISTEN step.

2. Starting three python HTTP server instances

In your working directory (any directory at your convenience), create a python file called backend.py and paste the following content to it. This is our simple HTTP python server.

#!/usr/bin/python

#backend.py
from BaseHTTPServer import BaseHTTPRequestHandler,HTTPServer
import sys
import logging

logging.basicConfig(filename='var/log/loadtest.log',level=logging.DEBUG,format='%(asctime)s %(message)s', datefmt='%m/%d/%Y %I:%M:%S %p')

#This class will handles any incoming request from the browser.
class myHandler(BaseHTTPRequestHandler):

    #Handler for the GET requests
    def do_GET(self):
        logging.debug("Request received for server on : %s " % PORT_NUMBER)
        self.send_response(200)
        self.send_header('Content-type','text/html')
        self.end_headers()
        # Send the html message
        self.wfile.write("Hello World: %s" % PORT_NUMBER)
        self.wfile.write("")
        return

try:
    #Create a web server and define the handler to manage the
    #incoming request
    PORT_NUMBER = int(sys.argv[1])
    server = HTTPServer(('', PORT_NUMBER), myHandler)
    print 'Started httpserver on port %s '  %  sys.argv[1]
    #Wait forever for incoming htto requests
    server.serve_forever()

except KeyboardInterrupt:
    print '^C received, shutting down the web server'
    server.socket.close()

Save the file.

Create a directory structure as follows inside your working directory.

var/

└── log

Next start 3 instances of HTTP python server as follows.

> nohup python backend.py 8080 &

> nohup python backend.py 8081 &

> nohup python backend.py 8082 &

Following is my console output.

Suhans-MacBook-Pro:NGINX suhanr$ nohup python backend.py 8080 &
[8] 94968
Suhans-MacBook-Pro:NGINX suhanr$ appending output to nohup.out
Suhans-MacBook-Pro:NGINX suhanr$ nohup python backend.py 8081 &
[9] 94969
Suhans-MacBook-Pro:NGINX suhanr$ appending output to nohup.out
Suhans-MacBook-Pro:NGINX suhanr$ nohup python backend.py 8082 &
[10] 94970
Suhans-MacBook-Pro:NGINX suhanr$ appending output to nohup.out

Verify the python HTTP server instances running ports as follows.

Suhans-MacBook-Pro:nginx suhanr$ lsof -i TCP:8080 | grep LISTEN
Python  97146 suhanr    5u  IPv4 0x4725c99a84b99059      0t0  TCP *:http-alt (LISTEN)
Suhans-MacBook-Pro:nginx suhanr$ lsof -i TCP:8081 | grep LISTEN
Python  97147 suhanr    5u  IPv4 0x4725c99a7ef91449      0t0  TCP *:sunproxyadmin (LISTEN)
Suhans-MacBook-Pro:nginx suhanr$ lsof -i TCP:8082 | grep LISTEN
Python  97162 suhanr    5u  IPv4 0x4725c99a8500d5e9      0t0  TCP *:us-cli (LISTEN)

3. Sending HTTP requests using cURL command embedded in a Shell script

Create a file called requestgen.sh and paste the following content to it.

#!/bin/bash
c=1
count=$1
echo $count
while [ $c -le $count ]
do
     curl http://localhost:8880/
     (( c++ ))
done

This will send pre determined number of HTTP requests to the 8880 port of which Nginx is listening.

Issue the following command.

> sh requestgen.sh 10

Suhans-MacBook-Pro:NGINX suhanr$ sh requestgen.sh 10
10
Hello World: 8082Hello World: 8080Hello World: 8081Hello World: 8082Hello World: 8080Hello World: 8081Hello World: 8082Hello World: 8080Hello World: 8081Hello World: 8082

4. Monitoring output

i. tail -f nohup.out

You will observe a similar output as follows.

Suhans-MacBook-Pro:NGINX suhanr$ tail -f nohup.out 
127.0.0.1 - - [30/Jun/2015 16:53:19] "GET / HTTP/1.0" 200 -
127.0.0.1 - - [30/Jun/2015 16:53:19] "GET / HTTP/1.0" 200 -
127.0.0.1 - - [30/Jun/2015 16:53:19] "GET / HTTP/1.0" 200 -
127.0.0.1 - - [30/Jun/2015 16:53:19] "GET / HTTP/1.0" 200 -
127.0.0.1 - - [30/Jun/2015 16:53:19] "GET / HTTP/1.0" 200 -
127.0.0.1 - - [30/Jun/2015 16:53:19] "GET / HTTP/1.0" 200 -
127.0.0.1 - - [30/Jun/2015 16:53:19] "GET / HTTP/1.0" 200 -
127.0.0.1 - - [30/Jun/2015 16:53:19] "GET / HTTP/1.0" 200 -
127.0.0.1 - - [30/Jun/2015 16:53:19] "GET / HTTP/1.0" 200 -
127.0.0.1 - - [30/Jun/2015 16:53:19] "GET / HTTP/1.0" 200 -

ii. tail -f var/log/loadtest.log

Suhans-MacBook-Pro:NGINX suhanr$ tail -f var/log/loadtest.log 
06/30/2015 05:10:14 PM Request received for server on : 8082 
06/30/2015 05:10:14 PM Request received for server on : 8080 
06/30/2015 05:10:14 PM Request received for server on : 8081 
06/30/2015 05:10:14 PM Request received for server on : 8082 
06/30/2015 05:10:14 PM Request received for server on : 8080 
06/30/2015 05:10:14 PM Request received for server on : 8081 
06/30/2015 05:10:14 PM Request received for server on : 8082 
06/30/2015 05:10:14 PM Request received for server on : 8080 
06/30/2015 05:10:14 PM Request received for server on : 8081 
06/30/2015 05:10:14 PM Request received for server on : 8082

5. Stopping servers

i. Stopping nginx

> nginx -s stop

i. Stopping python HTTP servers

Bring the processes to foreground by referring the job number.

You can find the job number from the console output shown above in section 2; refer the console output after starting the 3 python server instances.

Suhans-MacBook-Pro:NGINX suhanr$ fg 8
nohup python backend.py 8080
^CSuhans-MacBook-Pro:NGINX suhanr$ fg 9
nohup python backend.py 8081
^CSuhans-MacBook-Pro:NGINX suhanr$ fg 10
nohup python backend.py 8082
^CSuhans-MacBook-Pro:NGINX suhanr$ 

Then by issuing a Ctrl+C command you can stop the servers.

Then you can observe the following log entry in your nohup.out file.

Suhans-MacBook-Pro:NGINX suhanr$ tail -f nohup.out
Started httpserver on port 8080 
^C received, shutting down the web server
Started httpserver on port 8081 
^C received, shutting down the web server
Started httpserver on port 8082 
^C received, shutting down the web server

6. Errors

i. When starting Nginx, Address already in use error.

nginx: [emerg] bind() to 0.0.0.0:8080 failed (48: Address already in use)

Solution: Change the nginx installation directory nginx.conf files listen port to a different one. e.g.: 9980.

ii. loadtest.log not found

Solution: Create a directory structure var/log if you missed to create as instructed in step 2.

var/

└── log

    └── loadtest.log

Useful links:
[1] https://docs.wso2.com/display/CLUSTER420/Configuring+Nginx

WSO2 API Manager - Modify token API to return with Access-Control-Allow-Origin Response Header

By default API Manager is not returning Access-Control-Allow-Origin response header in token API.

You can easily do this by modifying the _TokenAPI_.xml at
<AM_HOME>/repository/deployment/server/synapse-configs/default/api/
by including the above property to the out sequence just before the send mediator.

I have tested this with AM 1.7.0 and please find the modified _TokenAPI_.xml as follows.

<api xmlns="http://ws.apache.org/ns/synapse" name="_WSO2AMTokenAPI_" context="/token">
    <resource methods="POST" url-mapping="/*" faultSequence="_token_fault_">
        <inSequence>
            <send>
                <endpoint>
                    <address uri="https://localhost:9443/oauth2/token"/>
                </endpoint>
            </send>
        </inSequence>
        <outSequence>
                <property name="Access-Control-Allow-Origin"
value="http://192.168.1.5:80,http://192.168.10.200:80,https://dev.wso2.com,https://sup.wso2.com"
scope="transport"
type="STRING"/>
            <send/>
        </outSequence>
    </resource>
    <handlers>
        <handler class="org.wso2.carbon.apimgt.gateway.handlers.ext.APIManagerCacheExtensionHandler"/>
    </handlers>
</api>

I have tested by sending a cURL request to this token API as follows.

curl -vk -d "grant_type=password&username=admin&password=admin" -H "Authorization: Basic Vnc5cXhhWHE5WGo1Wl8xdWVvc3FEbFN0d1RBYTpJTVNsV0ZOQ01KN1JmRmtPT1RpZF9iTWpWZlFh, Content-Type: application/x-www-form-urlencoded" https://localhost:8243/token

cURL command console output is as follows.

Suhans-MacBook-Pro:bin suhanr$ curl -vk -d "grant_type=password&username=admin&password=admin" -H "Authorization: Basic Vnc5cXhhWHE5WGo1Wl8xdWVvc3FEbFN0d1RBYTpJTVNsV0ZOQ01KN1JmRmtPT1RpZF9iTWpWZlFh, Content-Type: application/x-www-form-urlencoded" https://localhost:8243/token
* Hostname was NOT found in DNS cache
*   Trying 127.0.0.1...
* Connected to localhost (127.0.0.1) port 8243 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
* Server certificate: localhost
> POST /token HTTP/1.1
> User-Agent: curl/7.37.1
> Host: localhost:8243
> Accept: */*
> Authorization: Basic Vnc5cXhhWHE5WGo1Wl8xdWVvc3FEbFN0d1RBYTpJTVNsV0ZOQ01KN1JmRmtPT1RpZF9iTWpWZlFh, Content-Type: application/x-www-form-urlencoded
> Content-Length: 49
> Content-Type: application/x-www-form-urlencoded
>
* upload completely sent off: 49 out of 49 bytes
< HTTP/1.1 200 OK
< Access-Control-Allow-Origin: http://192.168.1.5:80,http://192.168.10.200:80,https://dev.wso2.com,https://sup.wso2.com
< Content-Type: application/json
< Pragma: no-cache
< Cache-Control: no-store
< Date: Fri, 26 Jun 2015 06:08:36 GMT
* Server WSO2-PassThrough-HTTP is not blacklisted
< Server: WSO2-PassThrough-HTTP
< Transfer-Encoding: chunked
<
* Connection #0 to host localhost left intact
{"scope":"default","token_type":"bearer","expires_in":3299,"refresh_token":"e8a1c130b372a0021f46bf9933a6a20","access_token":"e4fcf0346a647f10455b871630cba0fc"}

API Manager carbon log is as follows. To enable wirelogs on API Manager you can follow [1]. It is a similar process as ESB.

[2015-06-26 11:38:36,238] DEBUG - wire >> "POST /token HTTP/1.1[\r][\n]"
[2015-06-26 11:38:36,238] DEBUG - wire >> "User-Agent: curl/7.37.1[\r][\n]"
[2015-06-26 11:38:36,238] DEBUG - wire >> "Host: localhost:8243[\r][\n]"
[2015-06-26 11:38:36,238] DEBUG - wire >> "Accept: */*[\r][\n]"
[2015-06-26 11:38:36,238] DEBUG - wire >> "Authorization: Basic Vnc5cXhhWHE5WGo1Wl8xdWVvc3FEbFN0d1RBYTpJTVNsV0ZOQ01KN1JmRmtPT1RpZF9iTWpWZlFh, Content-Type: application/x-www-form-urlencoded[\r][\n]"
[2015-06-26 11:38:36,238] DEBUG - wire >> "Content-Length: 49[\r][\n]"
[2015-06-26 11:38:36,238] DEBUG - wire >> "Content-Type: application/x-www-form-urlencoded[\r][\n]"
[2015-06-26 11:38:36,238] DEBUG - wire >> "[\r][\n]"
[2015-06-26 11:38:36,239] DEBUG - wire >> "grant_type=password&username=admin&password=admin"
[2015-06-26 11:38:36,252] DEBUG - wire << "POST /oauth2/token HTTP/1.1[\r][\n]"
[2015-06-26 11:38:36,253] DEBUG - wire << "Authorization: Basic Vnc5cXhhWHE5WGo1Wl8xdWVvc3FEbFN0d1RBYTpJTVNsV0ZOQ01KN1JmRmtPT1RpZF9iTWpWZlFh, Content-Type: application/x-www-form-urlencoded[\r][\n]"
[2015-06-26 11:38:36,253] DEBUG - wire << "Content-Type: application/x-www-form-urlencoded[\r][\n]"
[2015-06-26 11:38:36,253] DEBUG - wire << "Accept: */*[\r][\n]"
[2015-06-26 11:38:36,253] DEBUG - wire << "Transfer-Encoding: chunked[\r][\n]"
[2015-06-26 11:38:36,253] DEBUG - wire << "Host: localhost:9443[\r][\n]"
[2015-06-26 11:38:36,253] DEBUG - wire << "Connection: Keep-Alive[\r][\n]"
[2015-06-26 11:38:36,253] DEBUG - wire << "User-Agent: Synapse-PT-HttpComponents-NIO[\r][\n]"
[2015-06-26 11:38:36,253] DEBUG - wire << "[\r][\n]"
[2015-06-26 11:38:36,253] DEBUG - wire << "31[\r][\n]"
[2015-06-26 11:38:36,254] DEBUG - wire << "grant_type=password&username=admin&password=admin[\r][\n]"
[2015-06-26 11:38:36,254] DEBUG - wire << "0[\r][\n]"
[2015-06-26 11:38:36,254] DEBUG - wire << "[\r][\n]"
[2015-06-26 11:38:36,349] DEBUG - wire >> "HTTP/1.1 200 OK[\r][\n]"
[2015-06-26 11:38:36,349] DEBUG - wire >> "Cache-Control: no-store[\r][\n]"
[2015-06-26 11:38:36,349] DEBUG - wire >> "Date: Fri, 26 Jun 2015 06:08:36 GMT[\r][\n]"
[2015-06-26 11:38:36,349] DEBUG - wire >> "Pragma: no-cache[\r][\n]"
[2015-06-26 11:38:36,350] DEBUG - wire >> "Content-Type: application/json[\r][\n]"
[2015-06-26 11:38:36,350] DEBUG - wire >> "Content-Length: 159[\r][\n]"
[2015-06-26 11:38:36,350] DEBUG - wire >> "Server: WSO2 Carbon Server[\r][\n]"
[2015-06-26 11:38:36,350] DEBUG - wire >> "[\r][\n]"
[2015-06-26 11:38:36,350] DEBUG - wire >> "{"scope":"default","token_type":"bearer","expires_in":3299,"refresh_token":"e8a1c130b372a0021f46bf9933a6a20","access_token":"e4fcf0346a647f10455b871630cba0fc"}"
[2015-06-26 11:38:36,352] DEBUG - wire << "HTTP/1.1 200 OK[\r][\n]"
[2015-06-26 11:38:36,352] DEBUG - wire << "Access-Control-Allow-Origin: http://192.168.1.5:80,http://192.168.10.200:80,https://dev.wso2.com,https://sup.wso2.com[\r][\n]"
[2015-06-26 11:38:36,352] DEBUG - wire << "Content-Type: application/json[\r][\n]"
[2015-06-26 11:38:36,352] DEBUG - wire << "Pragma: no-cache[\r][\n]"
[2015-06-26 11:38:36,352] DEBUG - wire << "Cache-Control: no-store[\r][\n]"
[2015-06-26 11:38:36,352] DEBUG - wire << "Date: Fri, 26 Jun 2015 06:08:36 GMT[\r][\n]"
[2015-06-26 11:38:36,352] DEBUG - wire << "Server: WSO2-PassThrough-HTTP[\r][\n]"
[2015-06-26 11:38:36,352] DEBUG - wire << "Transfer-Encoding: chunked[\r][\n]"
[2015-06-26 11:38:36,352] DEBUG - wire << "[\r][\n]"
[2015-06-26 11:38:36,353] DEBUG - wire << "9f[\r][\n]"
[2015-06-26 11:38:36,353] DEBUG - wire << "{"scope":"default","token_type":"bearer","expires_in":3299,"refresh_token":"e8a1c130b372a0021f46bf9933a6a20","access_token":"e4fcf0346a647f10455b871630cba0fc"}[\r][\n]"
[2015-06-26 11:38:36,353] DEBUG - wire << "0[\r][\n]"
[2015-06-26 11:38:36,353] DEBUG - wire << "[\r][\n]"

[1] http://suhan-opensource.blogspot.com/2015/03/how-to-get-wire-logs-from-wso2-esb.html

WSO2 ESB - Monitor DB operations with log4jdbc

Preparing the MySQL database

1. Install MySQL database if it isn’t installed on your computer.
2. Log in to MySQL using the following command.
> mysql -u root -p
Enter password: <rootPassword>

3. Issue the following commands to create the database regdb.
create database regdb;

Configuring WSO2 ESB

1. Download WSO2 ESB 4.8.1 from here. If you already have the product zip file (wso2esb-4.8.1.zip) continue with the next step.

2. Unzip the product to a path containing no spaces in the path name. This is your <ESB_HOME>

3. Download and add log4jdbc driver.

You can find the log4jdbc driver pre-built jar files from here.
I have used log4jdbc4-1.2.jar for this tutorial.

Download and copy it to <ESB_HOME>/repository/components/lib/ directory.

4. Open log4j.properties file from terminal.
> vi <ESB_HOME>/repository/conf/log4j.properties

Append below content at the end of log4j.properties file.

# Log all JDBC calls except for ResultSet calls
log4j.logger.jdbc.audit=INFO,jdbc
log4j.additivity.jdbc.audit=false

# Log only JDBC calls to ResultSet objects
log4j.logger.jdbc.resultset=INFO,jdbc
log4j.additivity.jdbc.resultset=false

# Log only the SQL that is executed.
log4j.logger.jdbc.sqlonly=DEBUG,sql
log4j.additivity.jdbc.sqlonly=false

# Log timing information about the SQL that is executed.
log4j.logger.jdbc.sqltiming=DEBUG,sqltiming
log4j.additivity.jdbc.sqltiming=false

# Log connection open/close events and connection number dump
log4j.logger.jdbc.connection=FATAL,connection
log4j.additivity.jdbc.connection=false

# the appender used for the JDBC API layer call logging above, sql only
log4j.appender.sql=org.apache.log4j.FileAppender
log4j.appender.sql.File=${carbon.home}/repository/logs/sql.log
log4j.appender.sql.Append=false
log4j.appender.sql.layout=org.apache.log4j.PatternLayout
log4j.appender.sql.layout.ConversionPattern=-----> %d{yyyy-MM-dd HH:mm:ss.SSS} %m%n%n

# the appender used for the JDBC API layer call logging above, sql timing
log4j.appender.sqltiming=org.apache.log4j.FileAppender
log4j.appender.sqltiming.File=${carbon.home}/repository/logs/sqltiming.log
log4j.appender.sqltiming.Append=false
log4j.appender.sqltiming.layout=org.apache.log4j.PatternLayout
log4j.appender.sqltiming.layout.ConversionPattern=-----> %d{yyyy-MM-dd HH:mm:ss.SSS} %m%n%n

# the appender used for the JDBC API layer call logging above
log4j.appender.jdbc=org.apache.log4j.FileAppender
log4j.appender.jdbc.File=${carbon.home}/repository/logs/jdbc.log
log4j.appender.jdbc.Append=false
log4j.appender.jdbc.layout=org.apache.log4j.PatternLayout
log4j.appender.jdbc.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss.SSS} %m%n

# the appender used for the JDBC Connection open and close events
log4j.appender.connection=org.apache.log4j.FileAppender
log4j.appender.connection.File=${carbon.home}/repository/logs/connection.log
log4j.appender.connection.Append=false
log4j.appender.connection.layout=org.apache.log4j.PatternLayout
log4j.appender.connection.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss.SSS} %m%n

5. Edit the default database configuration (data source definition configuration URL and driverClassName) defined in the  master-datasources.xml  file located at <ESB_HOME>/repository/conf/datasources directory.

<url>jdbc:log4jdbc:mysql://localhost:3306/regdb?autoReconnect=true</url>
<username>root</username>
<password>root</password>
<driverClassName>net.sf.log4jdbc.DriverSpy</driverClassName>

Please note that the previously created regdb database is used and my root password is "root".

6. Starting the WSO2 ESB server.

To create the tables in the MySQL database automatically upon server start, issue the following command.
Run the script wso2server.bat -Dsetup (on Windows) or wso2server.sh -Dsetup (on Linux/Solaris) from the <ESB_HOME>/bin folder.

7. Verify whether the database tables are created.

mysql>use regdb;
Database changed
mysql> show tables;
+-----------------------+
| Tables_in_ regdb      |
+-----------------------+
| REG_ASSOCIATION       |
| REG_CLUSTER_LOCK      |
| REG_COMMENT           |
| REG_CONTENT           |
| REG_CONTENT_HISTORY   |
| REG_LOG               |
| REG_PATH              |
| REG_PROPERTY          |
| REG_RATING            |
| REG_RESOURCE          |
| REG_RESOURCE_COMMENT  |
| REG_RESOURCE_HISTORY  |
| REG_RESOURCE_PROPERTY |
| REG_RESOURCE_RATING   |
| REG_RESOURCE_TAG      |
| REG_SNAPSHOT          |
| REG_TAG               |
| UM_ACCOUNT_MAPPING    |
| UM_CLAIM              |
| UM_DIALECT            |
| UM_DOMAIN             |
| UM_HYBRID_REMEMBER_ME |
| UM_HYBRID_ROLE        |
| UM_HYBRID_USER_ROLE   |
| UM_MODULE             |
| UM_MODULE_ACTIONS     |
| UM_PERMISSION         |
| UM_PROFILE_CONFIG     |
| UM_ROLE               |
| UM_ROLE_PERMISSION    |
| UM_SHARED_USER_ROLE   |
| UM_SYSTEM_ROLE        |
| UM_SYSTEM_USER        |
| UM_SYSTEM_USER_ROLE   |
| UM_TENANT             |
| UM_USER               |
| UM_USER_ATTRIBUTE     |
| UM_USER_PERMISSION    |
| UM_USER_ROLE          |
+-----------------------+
39 rows in set (0.00 sec)

View log files

1. Go to <ESB_HOME>/repository/logs
2. tail -f sqltiming.log
3. Perform DB operations and view query execution stats.

e.g.: create a user role "testrole" and view the log output.

-----> 2015-05-21 15:07:20.129  org.wso2.carbon.user.core.util.DatabaseUtil.getIntegerValueFromDatabase(DatabaseUtil.java:348)
1. SELECT UM_ID FROM UM_ROLE WHERE UM_ROLE_NAME='testrole' AND UM_TENANT_ID=-1234
 {executed in 0 msec}

-----> 2015-05-21 15:07:20.130  org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager.updateStringValuesToDatabase(JDBCUserStoreManager.java:2043)
1. INSERT INTO UM_ROLE (UM_ROLE_NAME, UM_TENANT_ID) VALUES ('testrole', -1234)
 {executed in 0 msec}

-----> 2015-05-21 15:07:20.133  org.wso2.carbon.user.core.util.DatabaseUtil.udpateUserRoleMappingInBatchMode(DatabaseUtil.java:497)
1. batching 0 statements:
 {executed in 0 msec}

WSO2 ESB - How to save a sequence in Registry

Go to ESB -> Main -> Manage -> Service Bus -> Sequences

Press add sequence

Configure your sequence and click on Save in Registry

Select Configuration Registry and click Save & Close button to save the sequence

WSO2 ESB java.lang.NullPointerException: Tenant domain has not been set in CarbonContext

When I try to invoke the secure service for NHTTP or PassThrough Transport I'm getting the following error.
WSO2 ESB wirelog is attached herewith for the reference.

[2015-05-05 11:42:11,044] DEBUG - wire >> "POST /services/StockQuoteProxy.StockQuoteProxyHttpsSoap11Endpoint HTTP/1.1[\r][\n]"
[2015-05-05 11:42:11,045] DEBUG - wire >> "Accept-Encoding: gzip,deflate[\r][\n]"
[2015-05-05 11:42:11,045] DEBUG - wire >> "Content-Type: text/xml;charset=UTF-8[\r][\n]"
[2015-05-05 11:42:11,045] DEBUG - wire >> "SOAPAction: "urn:getQuote"[\r][\n]"
[2015-05-05 11:42:11,045] DEBUG - wire >> "Content-Length: 416[\r][\n]"
[2015-05-05 11:42:11,046] DEBUG - wire >> "Host: 10.0.2.15:8243[\r][\n]"
[2015-05-05 11:42:11,046] DEBUG - wire >> "Connection: Keep-Alive[\r][\n]"
[2015-05-05 11:42:11,046] DEBUG - wire >> "User-Agent: Apache-HttpClient/4.1.1 (java 1.5)[\r][\n]"
[2015-05-05 11:42:11,046] DEBUG - wire >> "[\r][\n]"
[2015-05-05 11:42:11,046] DEBUG - wire >> "[\n]"
[2015-05-05 11:42:11,046] DEBUG - wire >> "   [\n]"
[2015-05-05 11:42:11,046] DEBUG - wire >> "   [\n]"
[2015-05-05 11:42:11,046] DEBUG - wire >> "      [\n]"
[2015-05-05 11:42:11,046] DEBUG - wire >> "         [\n]"
[2015-05-05 11:42:11,047] DEBUG - wire >> "         [\n]"
[2015-05-05 11:42:11,047] DEBUG - wire >> "            [\n]"
[2015-05-05 11:42:11,047] DEBUG - wire >> "            HTS[\n]"
[2015-05-05 11:42:11,047] DEBUG - wire >> "         [\n]"
[2015-05-05 11:42:11,047] DEBUG - wire >> "      [\n]"
[2015-05-05 11:42:11,047] DEBUG - wire >> "   [\n]"
[2015-05-05 11:42:11,047] DEBUG - wire >> ""
[2015-05-05 11:42:11,058] ERROR - ServerWorker Error processing POST request 
java.lang.NullPointerException: Tenant domain has not been set in CarbonContext
 at org.wso2.carbon.caching.impl.CacheManagerFactoryImpl.getCacheManager(CacheManagerFactoryImpl.java:79)
 at org.wso2.carbon.security.pox.POXSecurityHandler.getPOXCache(POXSecurityHandler.java:383)
 at org.wso2.carbon.security.pox.POXSecurityHandler.invoke(POXSecurityHandler.java:179)
 at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
 at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
 at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
 at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
 at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
 at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:459)
 at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:279)
 at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
[2015-05-05 11:42:11,069] DEBUG - wire << "HTTP/1.1 500 Internal Server Error[\r][\n]"
[2015-05-05 11:42:11,069] DEBUG - wire << "Content-Type: text/xml; charset=UTF-8[\r][\n]"
[2015-05-05 11:42:11,069] DEBUG - wire << "Date: Tue, 05 May 2015 06:12:11 GMT[\r][\n]"
[2015-05-05 11:42:11,069] DEBUG - wire << "Transfer-Encoding: chunked[\r][\n]"
[2015-05-05 11:42:11,069] DEBUG - wire << "Connection: Keep-Alive[\r][\n]"

Workaround for this issue is as follows.
Alter axis2.xml i.e move CarbonContentConfigurator as first entry in Transport.

<phase name="Transport">
<handler name="CarbonContentConfigurator"
class="org.wso2.carbon.mediation.initializer.handler.CarbonContextConfigurator"/>

Tested in ESB 4.8.0

How to view WSO2 ESB synapse configuration

WSO2 ESB version used: 4.8.1

1. Login to ESB.

2. Click source view under Main tab -> Manage -> Service Bus -> Source View

3. You can directly add proxies, sequences, endpoints and many more configurations from here.

Using file system as transport medium with WSO2 ESB VFS Transport

In this article I'm going to show you how to use the file system as transport medium using WSO2 ESB 4.8.1 VFS Transport.

Brief Overview of the scenario

By using sample SimpleStockQuoteService service we are going to test this scenario. We will send a SOAP request to the SimpleStockQuoteService and get the response back from it. Here both the request and the response will be saved in separate files.

I'm going to create a directory structure as follows.
Suhans-MacBook-Pro:test suhanr$ tree
.
├── in
├── original
└── out

i.e.,

1. /Users/suhanr/Desktop/test/in - Location to put SOAP request xml files to be processed.
2. /Users/suhanr/Desktop/test/original - Location to put processed xml files (which were in ../in folder before processing).
3. /Users/suhanr/Desktop/test/out - Location to store the responses received from service as xml files.

Our proxy will automatically poll for files in the given location (i.e. ../in location above). I have set the transport.PollInterval to 15 seconds in this scenario which is the default interval. You don't have to know about this parameter to followup this article.

If a file is found in ../in location, it will be processed and will be moved to ../original folder then the response is saved in a file in ../out folder.

Steps to follow

1. Get a fresh WSO2 ESB 4.8.1 pack. You can download it from here [1].

2. Extract it to any directory convenient to you (without containing spaces to the path of your extracted folder). Lets call this path ESB_HOME.
e.g.: my ESB_HOME > /WSO2/ESB/demo/simplevfs/wso2esb-4.8.1

3. Prepare the SimpleStockQuoteService service [2].

i) Go to ESB_HOME/samples/axis2Server/src/SimpleStockQuoteService
you can see the files and folders as follows.
build.xml conf      src

ii) Issue an ant command to build the SimpleStockQuoteService.aar

Suhans-MacBook-Pro:SimpleStockQuoteService suhanr$ ant
Buildfile: /WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/samples/axis2Server/src/SimpleStockQuoteService/build.xml

clean:

init:
    [mkdir] Created dir: /WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/samples/axis2Server/src/SimpleStockQuoteService/temp
    [mkdir] Created dir: /WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/samples/axis2Server/src/SimpleStockQuoteService/temp/classes
    [mkdir] Created dir: /WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/samples/axis2Server/repository/services
compile-all:
    [javac] /WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/samples/axis2Server/src/SimpleStockQuoteService/build.xml:47: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds
    [javac] Compiling 9 source files to /WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/samples/axis2Server/src/SimpleStockQuoteService/temp/classes
build-service:
    [mkdir] Created dir: /WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/samples/axis2Server/src/SimpleStockQuoteService/temp/SimpleStockQuote
    [mkdir] Created dir: /WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/samples/axis2Server/src/SimpleStockQuoteService/temp/SimpleStockQuote/META-INF
     [copy] Copying 1 file to /WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/samples/axis2Server/src/SimpleStockQuoteService/temp/SimpleStockQuote/META-INF
     [copy] Copying 9 files to /WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/samples/axis2Server/src/SimpleStockQuoteService/temp/SimpleStockQuote
      [jar] Building jar: /WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/samples/axis2Server/repository/services/SimpleStockQuoteService.aar
BUILD SUCCESSFUL
Total time: 1 second

Now your SimpleStockQuoteService.aar jar is copied to services.

4. Start axis2 server

i) Go to ESB_HOME/samples/axis2Server.

ii) Start server by issuing the following command.

Suhans-MacBook-Pro:axis2Server suhanr$ sh axis2server.sh 
 Using JAVA_HOME:   /Library/Java/JavaVirtualMachines/jdk1.7.0_67.jdk/Contents/Home
 Using AXIS2 Repository :   /WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/samples/axis2Server/repository
 Using AXIS2 Configuration :   /WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/samples/axis2Server/repository/conf/axis2.xml
15/03/20 10:41:31 INFO util.SampleAxis2ServerManager: [SimpleAxisServer] Starting
[SimpleAxisServer] Using the Axis2 Repository : /WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/samples/axis2Server/repository
[SimpleAxisServer] Using the Axis2 Configuration File : /WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/samples/axis2Server/repository/conf/axis2.xml
15/03/20 10:41:31 INFO deployment.ModuleDeployer: Deploying module: addressing - file:/WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/samples/axis2Server/repository/modules/addressing.mar
15/03/20 10:41:31 INFO deployment.ModuleDeployer: Deploying module: rampart - file:/WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/samples/axis2Server/repository/modules/rampart.mar
15/03/20 10:41:32 INFO deployment.ModuleDeployer: Deploying module: sandesha2 - file:/WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/samples/axis2Server/repository/modules/sandesha2.mar
15/03/20 10:41:32 INFO deployment.ModuleDeployer: Deploying module: addressing - file:/WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/repository/components/plugins/org.wso2.carbon.addressing_4.2.0.jar
15/03/20 10:41:32 INFO deployment.ModuleDeployer: Deploying module: wso2caching - file:/WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/repository/components/plugins/org.wso2.carbon.caching.core_4.2.0.jar
15/03/20 10:41:32 INFO deployment.ModuleDeployer: Deploying module: ComponentMgtModule - file:/WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/repository/components/plugins/org.wso2.carbon.feature.mgt.services_4.2.0.jar
15/03/20 10:41:32 INFO deployment.ModuleDeployer: Deploying module: wso2mex - file:/WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/repository/components/plugins/org.wso2.carbon.mex_4.2.0.jar
15/03/20 10:41:32 INFO deployment.ModuleDeployer: Deploying module: pagination - file:/WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/repository/components/plugins/org.wso2.carbon.registry.server_4.2.0.jar
15/03/20 10:41:32 INFO deployment.ModuleDeployer: Deploying module: relay - file:/WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/repository/components/plugins/org.wso2.carbon.relay.module_4.2.0.jar
15/03/20 10:41:32 INFO deployment.ModuleDeployer: Deploying module: sandesha2 - file:/WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/repository/components/plugins/org.wso2.carbon.rm_4.2.0.jar
15/03/20 10:41:32 INFO deployment.ModuleDeployer: Deploying module: POXSecurityModule - file:/WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/repository/components/plugins/org.wso2.carbon.security.mgt_4.2.2.jar
15/03/20 10:41:32 INFO deployment.ModuleDeployer: Deploying module: ServerAdminModule - file:/WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/repository/components/plugins/org.wso2.carbon.server.admin_4.2.0.jar
15/03/20 10:41:32 INFO deployment.ModuleDeployer: Deploying module: wso2statistics - file:/WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/repository/components/plugins/org.wso2.carbon.statistics_4.2.2.jar
15/03/20 10:41:32 INFO deployment.ModuleDeployer: Deploying module: wso2throttle - file:/WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/repository/components/plugins/org.wso2.carbon.throttle.core_4.2.0.jar
15/03/20 10:41:32 INFO deployment.ModuleDeployer: Deploying module: usagethrottling - file:/WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/repository/components/plugins/org.wso2.carbon.throttling.agent_2.2.0.jar
15/03/20 10:41:32 INFO deployment.ModuleDeployer: Deploying module: wso2tracer - file:/WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/repository/components/plugins/org.wso2.carbon.tracer_4.2.0.jar
15/03/20 10:41:32 INFO deployment.ModuleDeployer: Deploying module: metering - file:/WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/repository/components/plugins/org.wso2.carbon.usage.agent_2.2.0.jar
15/03/20 10:41:32 INFO deployment.ModuleDeployer: Deploying module: wso2xfer - file:/WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/repository/components/plugins/org.wso2.carbon.xfer_4.2.0.jar
15/03/20 10:41:32 INFO deployment.ModuleDeployer: Deploying module: rampart - file:/WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/repository/components/plugins/rampart-core_1.6.1.wso2v12.jar
15/03/20 10:41:32 INFO deployment.ModuleDeployer: Deploying module: rahas - file:/WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/repository/components/plugins/rampart-trust_1.6.1.wso2v12.jar
15/03/20 10:41:32 ERROR sandesha2.SandeshaModule: Could not load module policies. Using default values.
15/03/20 10:41:32 INFO config.ClientConnFactoryBuilder: HTTPS Loading Identity Keystore from : ../../repository/resources/security/wso2carbon.jks
15/03/20 10:41:32 INFO config.ClientConnFactoryBuilder: HTTPS Loading Trust Keystore from : ../../repository/resources/security/client-truststore.jks
15/03/20 10:41:32 INFO nhttp.HttpCoreNIOSender: HTTPS Sender starting
15/03/20 10:41:32 INFO nhttp.HttpCoreNIOSender: HTTP Sender starting
15/03/20 10:41:32 INFO jms.JMSSender: JMS Sender started
15/03/20 10:41:32 INFO jms.JMSSender: JMS Transport Sender initialized...
15/03/20 10:41:32 INFO deployment.DeploymentEngine: Deploying Web service: SimpleStockQuoteService.aar - file:/WSO2/ESB/demo/simplevfs/wso2esb-4.8.1/samples/axis2Server/repository/services/SimpleStockQuoteService.aar
15/03/20 10:41:33 INFO nhttp.HttpCoreNIOListener: HTTPS Listener started on 0:0:0:0:0:0:0:0:9002
15/03/20 10:41:33 INFO nhttp.HttpCoreNIOListener: HTTP Listener started on 0:0:0:0:0:0:0:0:9000
15/03/20 10:41:33 INFO util.SampleAxis2ServerManager: [SimpleAxisServer] Started

5. Configure VFS Transport
It is time to configure your VFS Transport in axis2.xml file [3]

i) Go to ESB_HOME/repository/conf/axis2

ii) Open axis2.xml file to edit

Suhans-MacBook-Pro:wso2esb-4.8.1 suhanr$ vi repository/conf/axis2/axis2.xml

iii) Uncomment the VFS listener and VFS sender as follows.

<transportreceiver name="vfs" class="org.apache.synapse.transport.vfs.VFSTransportListener"/>
...
<transportSender name="vfs" class="org.apache.synapse.transport.vfs.VFSTransportSender"/>

iv) Save the changes

6. Create the SOAP request input xml file

i) Create the folder structure as already shown in the overview section at the top of this article. You can rename these folders as you like and can create anywhere which is accessible by the server.
i.e. 3 folders namely, in, original and out.

ii) Go to ../in folder that you have created and create a file named test.xml and copy the following content to it.

<?xml version='1.0' encoding='UTF-8'?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing">
    <soapenv:Body>
        <m0:getQuote xmlns:m0="http://services.samples">
            <m0:request>
                <m0:symbol>WSO2</m0:symbol>
            </m0:request>
        </m0:getQuote>
    </soapenv:Body>
</soapenv:Envelope>

7. After adding the StockQuoteProxy proxy configuration, your ESB synapse configuration will look like as follows.

<?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="StockQuoteProxy" transports="vfs" startOnLoad="true">
      <target>
         <endpoint>
            <address uri="http://localhost:9000/services/SimpleStockQuoteService"
                     format="soap12"/>
         </endpoint>
         <outSequence>
            <property name="transport.vfs.ReplyFileName"
                      expression="fn:concat(fn:substring-after(get-property('MessageID'), 'urn:uuid:'), '.xml')"
                      scope="transport"/>
            <property name="OUT_ONLY" value="true"/>
            <send>
               <endpoint>
                  <address uri="vfs:file:///Users/suhanr/Desktop/test/out"/>
               </endpoint>
            </send>
         </outSequence>
      </target>
      <publishWSDL uri="file:repository/samples/resources/proxy/sample_proxy_1.wsdl"/>
      <parameter name="transport.PollInterval">15</parameter>
      <parameter name="transport.vfs.ActionAfterProcess">MOVE</parameter>
      <parameter name="transport.vfs.FileURI">file:///Users/suhanr/Desktop/test/in</parameter>
      <parameter name="transport.vfs.MoveAfterProcess">file:///Users/suhanr/Desktop/test/original</parameter>
      <parameter name="transport.vfs.MoveAfterFailure">file:///Users/suhanr/Desktop/test/original</parameter>
      <parameter name="transport.vfs.FileNamePattern">.*\.xml</parameter>
      <parameter name="transport.vfs.ContentType">text/xml</parameter>
      <parameter name="transport.vfs.ActionAfterFailure">MOVE</parameter>
   </proxy>
   <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>
</definitions>

You can copy this configuration easily by clicking on the "view plain" link at the top left corner of the code view.

Once you save the configuration, within 15 seconds time your file will be processed. Now lets verify the results.

Analysing the output

Once you save your configuration, ESB console output will be as follows.

[2015-03-20 11:32:53,581]  INFO - SynapseTaskManager Shutting down the task manager
[2015-03-20 11:32:53,583]  INFO - XMLConfigurationBuilder Generating the Synapse configuration model by parsing the XML configuration
[2015-03-20 11:32:53,589]  INFO - ProxyService Building Axis service for Proxy service : StockQuoteProxy
[2015-03-20 11:32:53,610]  INFO - ProxyService Adding service StockQuoteProxy to the Axis2 configuration
[2015-03-20 11:32:53,622]  INFO - DeploymentInterceptor Deploying Axis2 service: StockQuoteProxy {super-tenant}
[2015-03-20 11:32:53,695]  INFO - ProxyService Successfully created the Axis2 service for Proxy service : StockQuoteProxy

When the file is processed, you can see this output in your simple Axis2 server console.

Fri Mar 20 11:33:08 IST 2015 samples.services.SimpleStockQuoteService :: Generating quote for : WSO2

Check your folder tree structure as follows.
Suhans-MacBook-Pro:test suhanr$ tree
.
├── in
├── original
│   ├── test.xml
└── out
    └── a9b795da-a668-4b6a-ac8a-90db42d7311d.xml

As you can see the test.xml file is processed and moved to the ../original folder.
The response received from the StockQuoteProxy is placed in ../out folder as a9b795da-a668-4b6a-ac8a-90db42d7311d.xml

Response file contents is as follows.

   
      
         
            -2.378108963314817
            12.594090499041867
            -79.46865111676226
            79.76869958422132
            Fri Mar 20 11:33:08 IST 2015
            -79.2594140983345
            -7611066.458300805
            WSO2 Company
            81.77710215829231
            24.900435994896995
            3.054782179111802
            -77.84872452039339
            WSO2
            7308
         
      
   

Improvements

You can store the endpoint in governance registry or configuration registry [4].

e.g.: Governance registry endpoint: "StockQuoteEP"

<endpoint xmlns="http://ws.apache.org/ns/synapse">
   <address uri="http://localhost:9000/services/SimpleStockQuoteService" format="soap12">
      <suspendOnFailure>
         <progressionFactor>1.0</progressionFactor>
      </suspendOnFailure>
      <markForSuspension>
         <retriesBeforeSuspension>0</retriesBeforeSuspension>
         <retryDelay>0</retryDelay>
      </markForSuspension>
   </address>
</endpoint>

Modified proxy service will be as follows.

<?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="StockQuoteProxy" transports="vfs" startOnLoad="true">
      <target>
         <endpoint key="gov:/StockQuoteEP"/>
         <outSequence>
            <property name="transport.vfs.ReplyFileName"
                      expression="fn:concat(fn:substring-after(get-property('MessageID'), 'urn:uuid:'), '.xml')"
                      scope="transport"/>
            <property name="OUT_ONLY" value="true"/>
            <send>
               <endpoint>
                  <address uri="vfs:file:///Users/suhanr/Desktop/test/out"/>
               </endpoint>
            </send>
         </outSequence>
      </target>
      <publishWSDL uri="file:repository/samples/resources/proxy/sample_proxy_1.wsdl"/>
      <parameter name="transport.PollInterval">15</parameter>
      <parameter name="transport.vfs.ActionAfterProcess">MOVE</parameter>
      <parameter name="transport.vfs.FileURI">file:///Users/suhanr/Desktop/test/in</parameter>
      <parameter name="transport.vfs.MoveAfterProcess">file:///Users/suhanr/Desktop/test/original</parameter>
      <parameter name="transport.vfs.MoveAfterFailure">file:///Users/suhanr/Desktop/test/original</parameter>
      <parameter name="transport.vfs.FileNamePattern">.*\.xml</parameter>
      <parameter name="transport.vfs.ContentType">text/xml</parameter>
      <parameter name="transport.vfs.ActionAfterFailure">MOVE</parameter>
   </proxy>
   <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>
</definitions>

Future Improvements

ESB 4.8.1 DOES NOT support fetching transport.vfs.FileURI from registry (Currently ESB does not support fetching service parameters from registry).
However in the next release i.e. ESB 4.9.0 we will be able to cater this requirement through inboundEndpoint [5].

Sample configuration is given below as per [5] (Applicable to ESB 4.9.0 and later releases only).
Please note that the inboundEndpoint configuration shown below is subjected to change since ESB 4.9.0 is not released at the time of writing this article.

<inboundEndpoint xmlns="http://ws.apache.org/ns/synapse";  name="wso2File"
 sequence="request"  onError="fault"  protocol="file"
 suspend="false">
   <parameters>
      <parameter name="interval">1000</parameter>
      <parameter name="transport.vfs.ActionAfterErrors">NONE</parameter>
      <parameter name="transport.vfs.LockReleaseSameNode">false</parameter>
      <parameter name="transport.vfs.AutoLockRelease">false</parameter>
      <parameter name="transport.vfs.ActionAfterFailure">NONE</parameter>
      <parameter name="transport.vfs.ActionAfterProcess">NONE</parameter>
      <parameter name="sequential">false</parameter>
      <parameter name="transport.vfs.FileURI"
*key="conf:/repository/esb/esb-configurations/test"*/>
      <parameter name="transport.vfs.DistributedLock">false</parameter>
      <parameter name="transport.vfs.Locking">enable</parameter>
   </parameters>
</inboundEndpoint

Summary

In this article we have looked at using the file system as a transport medium using WSO2 ESB 4.8.1 VFS Transport. For this use case we have used the Sample SimpleStockQuoteService service. SOAP request is stored in an xml file and the response received from the SimpleStockQuoteService is also stored in an xml file.

Links

[1] http://wso2.com/products/enterprise-service-bus/

[2] https://docs.wso2.com/display/ESB451/ESB+Samples+Setup#ESBSamplesSetup-StartingSampleBack-EndServices

[3] https://docs.wso2.com/display/ESB481/VFS+Transport#VFSTransport-enableVFSEnablingthetransport
[4] http://suhan-opensource.blogspot.com/2015/05/wso2-esb-how-to-save-sequence-in.html
[5] https://www.mail-archive.com/dev@wso2.org/msg44308.html

How to get wire logs from WSO2 ESB

When working with WSO2 Enterprise Service Bus, sometimes we need to see/analyze the HTTP messages coming to ESB and going out from ESB.

Without installing third party software to view these messages we can use WSO2 ESB built-in wire log functionality.

By enabling wire logs for Passthrough http transport in ESB we can easily exploit this capability.
I'm using ESB 4.8.0 for my testing in this article.

WSO2 ESB Configuration changes

Here are the steps to enable wire logs in ESB.

1. Open log4j.properties file from terminal.
> vi <ESB_HOME>/repository/conf/log4j.properties

2. Find the following line, comment out and save the changes to the log4j.properties file.

log4j.logger.org.apache.synapse.transport.http.wire=DEBUG

3. Start/Restart ESB server

> sh <ESB_HOME>/bin/wso2server.sh

Now you are ready to view wire logs from WSO2 ESB.

Creating a service request and getting the response

I have used the echo proxy in WSO2 ESB for my testing.

Using SOAP UI, I have sent the following SOAP message to the WSO2 ESB echo proxy service [1] SOAP endpoint.

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:echo="http://echo.services.core.carbon.wso2.org">

   <soapenv:Header/>

   <soapenv:Body>

      <echo:echoString>

         <in>Suhan says hi!</in>

      </echo:echoString>

   </soapenv:Body>

</soapenv:Envelope>

I got the following response from ESB echo proxy service.

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">

   <soapenv:Body>

      <ns:echoStringResponse xmlns:ns="http://echo.services.core.carbon.wso2.org">

         <return>Suhan says hi!</return>

      </ns:echoStringResponse>

   </soapenv:Body>

</soapenv:Envelope>

Reading the wire logs from WSO2 ESB console

Following is the output from the WSO2 ESB console I have obtained.

[2015-03-16 16:36:16,665] DEBUG - wire >> "POST /services/echo.echoHttpSoap11Endpoint HTTP/1.1[\r][\n]"

[2015-03-16 16:36:16,668] DEBUG - wire >> "Accept-Encoding: gzip,deflate[\r][\n]"

[2015-03-16 16:36:16,668] DEBUG - wire >> "Content-Type: text/xml;charset=UTF-8[\r][\n]"

[2015-03-16 16:36:16,669] DEBUG - wire >> "SOAPAction: "urn:echoString"[\r][\n]"

[2015-03-16 16:36:16,669] DEBUG - wire >> "Content-Length: 317[\r][\n]"

[2015-03-16 16:36:16,669] DEBUG - wire >> "Host: Suhans-MacBook-Pro.local:8280[\r][\n]"

[2015-03-16 16:36:16,669] DEBUG - wire >> "Connection: Keep-Alive[\r][\n]"

[2015-03-16 16:36:16,669] DEBUG - wire >> "User-Agent: Apache-HttpClient/4.1.1 (java 1.5)[\r][\n]"

[2015-03-16 16:36:16,669] DEBUG - wire >> "[\r][\n]"

[2015-03-16 16:36:16,669] DEBUG - wire >> "<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:echo="http://echo.services.core.carbon.wso2.org">[\n]"

[2015-03-16 16:36:16,669] DEBUG - wire >> "   <soapenv:Header/>[\n]"

[2015-03-16 16:36:16,670] DEBUG - wire >> "   <soapenv:Body>[\n]"

[2015-03-16 16:36:16,670] DEBUG - wire >> "      <echo:echoString>[\n]"

[2015-03-16 16:36:16,670] DEBUG - wire >> "         <!--Optional:-->[\n]"

[2015-03-16 16:36:16,670] DEBUG - wire >> "         <in>Suhan says hi!</in>[\n]"

[2015-03-16 16:36:16,670] DEBUG - wire >> "      </echo:echoString>[\n]"

[2015-03-16 16:36:16,670] DEBUG - wire >> "   </soapenv:Body>[\n]"

[2015-03-16 16:36:16,671] DEBUG - wire >> "</soapenv:Envelope>"

[2015-03-16 16:36:16,726] DEBUG - wire << "HTTP/1.1 200 OK[\r][\n]"

[2015-03-16 16:36:16,726] DEBUG - wire << "Content-Type: text/xml; charset=UTF-8[\r][\n]"

[2015-03-16 16:36:16,726] DEBUG - wire << "Date: Mon, 16 Mar 2015 11:06:16 GMT[\r][\n]"

[2015-03-16 16:36:16,727] DEBUG - wire << "Server: WSO2-PassThrough-HTTP[\r][\n]"

[2015-03-16 16:36:16,727] DEBUG - wire << "Transfer-Encoding: chunked[\r][\n]"

[2015-03-16 16:36:16,727] DEBUG - wire << "Connection: Keep-Alive[\r][\n]"

[2015-03-16 16:36:16,727] DEBUG - wire << "[\r][\n]"

[2015-03-16 16:36:16,730] DEBUG - wire << "125[\r][\n]"

[2015-03-16 16:36:16,730] DEBUG - wire << "<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><ns:echoStringResponse xmlns:ns="http://echo.services.core.carbon.wso2.org"><return>Suhan says hi!</return></ns:echoStringResponse></soapenv:Body></soapenv:Envelope>[\r][\n]"

[2015-03-16 16:36:16,731] DEBUG - wire << "0[\r][\n]"

[2015-03-16 16:36:16,731] DEBUG - wire << "[\r][\n]"

Now lets see how to identify the message direction from this console output.

As you may already know there have to be messages coming to ESB from wire and going out to wire from ESB.

Following indicates the messages coming to ESB from wire.

DEBUG - wire >> "POST /services...... 

Following indicates the messages going to wire from ESB.

DEBUG - wire << "HTTP/1.1 200 OK.......

Why see wire logs?

• Troubleshoot unexpected issues in integrated systems. 
• Whether the correct payload is going out from ESB. e.g.: Whether the Content-type HTTP headers are properly set in out going messages.
• Whether the correct SOAP messages coming to ESB. e.g.: Corrupted, malformed...

Note: This configuration change only applicable to WSO2 ESB 4.7.0 or higher versions.

Note: We DO NOT recommend running production systems with wire logs enabled. Wire logs should be enabled ONLY for the troubleshooting purposes.

[1] http://suhans-macbook-pro.local:8280/services/echo?wsdl

How to free up your Google Drive storage quickly.

Well, I got a warning saying my quota has exceeded this morning. :(
I have 30GB Google Drive Storage plan.
My current capacity has moved up to 30.12GB!

According to the Google Drive Storage capacity pie chart summary [1], most space is consumed by my Gmail!

Now I wanted to find a way to quickly delete emails which are having large attachments.

BEFORE YOU ATTEMPT THIS MAKE SURE YOU HAVE BACKED UP NECESSARY EMAILS LOCALLY.

This is how to delete your email messages which are taking up more space on your google drive storage.

Type the following in gmail search box to search your Inbox for messages larger than a given size, say 10MB.
larger:10m

Then Select All messages by clicking the select all check box as shown below.

As you can see there are large number of messages in other pages, only 50 conversations are selected in this page.
Note that in my case, there is a link saying "Select all 36,603 conversations in Inbox"

Click on it to select all messages which are taking more than your mentioned space (10MB).

Now delete your messages by clicking on the trash bin icon.

Delete these messages from your Trash folder also [THIS WILL DELETE THESE MESSAGES FOREVER IN AN INSTANT, YOU CANNOT RESTORE THESE MESSAGES HEREAFTER FROM TRASH].

Now you can see that your used space has reduced [1].
Your space will be freed-up as follows. :)

After deleting messages taking up more space than 7 MB, my storage capacity summary as follows.

After deleting messages taking up more space than 5 MB, my storage capacity summary as follows.

[1] https://www.google.com/settings/storage

How to quickly transfer your files between computers using Python SimpleHTTPServer

Sometimes we need to share a file quickly in a folder with a colleague while at work.

Well if you have apple devices, you can quickly share files and folders with AirDrop.

But what if you have a mix of operating systems and you don't have a portable HDD or a USB
pen drive at vicinity?

If you have python installed in your operating system by default,
here's how to do it quickly and easily...

Two computers I'm using are having OS X Yosemite and Ubuntu operating systems.
I'm trying to share a file in a given folder at my OS X Mac and download it from a web browser from my friend's ubuntu computer.

From my computer

1. Go to the folder from a terminal session.

2. Find the IP address of the computer that the file is in.
> ifconfig
Note: my IP is 10.100.5.175

3. Issue the following command to start the python SimpleHTTPServer.
> python -m SimpleHTTPServer
Note: server starting on port 8000 [1].

From my friend's computer

4. From the ubuntu computer (10.100.0.101) open web browser and access the following URL.
http://10.100.5.175:8000/

5. Select the file you want and download.

Note: observe the request coming to the python SimpleHTTPServer from terminal [2].

[1]
Suhans-MacBook-Pro:compressed suhanr$ python -m SimpleHTTPServer
Serving HTTP on 0.0.0.0 port 8000 ...
[2]
10.100.0.101 - - [10/Mar/2015 10:14:27] "GET / HTTP/1.1" 200 -
10.100.0.101 - - [10/Mar/2015 10:14:27] code 404, message File not found
10.100.0.101 - - [10/Mar/2015 10:14:27] "GET /favicon.ico HTTP/1.1" 404 -
10.100.0.101 - - [10/Mar/2015 10:14:33] "GET /wso2is-5.0.0.zip HTTP/1.1" 200 -

Browse built-in H2 database of WSO2 Products

WSO2 products in default are shipped with H2 database which is good for development, testing, experimental work and for some production systems. WSO2 products also support industry-standard RDBMS such as Oracle, PostgreSQL, MySQL, MS SQL.

When you develop, test and experiment with default H2 database, sometimes you want to go inside the database and see.

And this is how to do it.

1. Go to the <PRODUCT_HOME>/repository/conf/

2. Open the carbon.xml file to edit.

3. Enable the H2DatabaseConfiguration as follows and Save changes.


<H2DatabaseConfiguration>
        <property name="web"/>
        <property name="webPort">8082</property>
        <property name="webAllowOthers"/>        
</H2DatabaseConfiguration>

4. Go to <PRODUCT_HOME>/bin and start the the server as follows.
    e.g.: > sh wso2server.sh

5. Open URL http://localhost:8082/ from browser.

6. Complete the following fields with appropriate values.
Driver Class: org.h2.Driver
JDBC URL  : jdbc:h2:<PRODUCT_HOME>/repository/database/WSO2CARBON_DB
Username    : wso2carbon
Password     : wso2carbon

7. Once you connect to the database you will see a similar UI as follows.

In this example I have used WSO2 API Manager 1.7.0 and connected to the WSO2AM_DB database at <product_home>/repository/database/WSO2AM_DB

Search Gmail from Sender without listing Chat messages

Simply type this on your gmail search box

from:friend@firm.com !in:chat 

Generate JAX-WS client from WSDL file/URL using wsimport tool

wsimport tool available in $JDK/bin folder.

We can use this wsimport tool to parse a certain WSDL file of the server and generate client files (JAX-WS portable artifacts) to access server's published service.

Suhans-MacBook-Pro:client suhanr$ ls
RemoteUserStoreManagerService.wsdl
Suhans-MacBook-Pro:client suhanr$ wsimport -d /WSO2/wsimport_test/client/ RemoteUserStoreManagerService.wsdl
parsing WSDL...

[WARNING] src-resolve: Cannot resolve the name 'ax2605:UserStoreException' to a(n) 'type definition' component.
  line 83 of file:/WSO2/wsimport_test/client/RemoteUserStoreManagerService.wsdl#types?schema4

[WARNING] src-resolve: Cannot resolve the name 'ax2609:ClaimDTO' to a(n) 'type definition' component.
  line 147 of file:/WSO2/wsimport_test/client/RemoteUserStoreManagerService.wsdl#types?schema4

[WARNING] src-resolve: Cannot resolve the name 'ax2612:Tenant' to a(n) 'type definition' component.
  line 462 of file:/WSO2/wsimport_test/client/RemoteUserStoreManagerService.wsdl#types?schema4

[WARNING] Ignoring SOAP port "RemoteUserStoreManagerServiceHttpsSoap12Endpoint": it uses non-standard SOAP 1.2 binding.
You must specify the "-extension" option to use this binding.
  line 1785 of file:/WSO2/wsimport_test/client/RemoteUserStoreManagerService.wsdl

[WARNING] ignoring port "RemoteUserStoreManagerServiceHttpsEndpoint": no SOAP address specified. try running wsimport with -extension switch.
  line 1788 of file:/WSO2/wsimport_test/client/RemoteUserStoreManagerService.wsdl

[WARNING] src-resolve: Cannot resolve the name 'ax2605:UserStoreException' to a(n) 'type definition' component.
  line 83 of file:/WSO2/wsimport_test/client/RemoteUserStoreManagerService.wsdl#types?schema4

[WARNING] src-resolve: Cannot resolve the name 'ax2609:ClaimDTO' to a(n) 'type definition' component.
  line 147 of file:/WSO2/wsimport_test/client/RemoteUserStoreManagerService.wsdl#types?schema4

[WARNING] src-resolve: Cannot resolve the name 'ax2612:Tenant' to a(n) 'type definition' component.
  line 462 of file:/WSO2/wsimport_test/client/RemoteUserStoreManagerService.wsdl#types?schema4

generating code...

compiling code...

If you are locally having the server up and running, get the wsdl link and make sure it is accessible via local web browser.

Your command may look like this,

Suhans-MacBook-Pro:client suhanr$ wsimport -d /WSO2/wsimport_test/client/ http://localhost:9763/services/RemoteUserStoreManagerService?wsdl

After generating the code,

Suhans-MacBook-Pro:client suhanr$ tree

.

├── RemoteUserStoreManagerService.wsdl

└── org

    └── wso2

        └── carbon

            ├── um

            │   └── ws

            │       └── service

            │           ├── AddRole.class

            │           ├── AddUser.class

            │           ├── AddUserClaimValue.class

            │           ├── AddUserClaimValues.class

            │           ├── ArrayOfString.class

            │           ├── Authenticate.class

            │           ├── AuthenticateResponse.class

            │           ├── DeleteRole.class

            │           ├── DeleteUser.class

            │           ├── DeleteUserClaimValue.class

            │           ├── DeleteUserClaimValues.class

            │           ├── GetAllProfileNames.class

            │           ├── GetAllProfileNamesResponse.class

            │           ├── GetHybridRoles.class

            │           ├── GetHybridRolesResponse.class

            │           ├── GetPasswordExpirationTime.class

            │           ├── GetPasswordExpirationTimeResponse.class

            │           ├── GetProfileNames.class

            │           ├── GetProfileNamesResponse.class

            │           ├── GetProperties.class

            │           ├── GetPropertiesResponse.class

            │           ├── GetRoleListOfUser.class

            │           ├── GetRoleListOfUserResponse.class

            │           ├── GetRoleNames.class

            │           ├── GetRoleNamesResponse.class

            │           ├── GetTenantId.class

            │           ├── GetTenantIdResponse.class

            │           ├── GetTenantIdofUser.class

            │           ├── GetTenantIdofUserResponse.class

            │           ├── GetUserClaimValue.class

            │           ├── GetUserClaimValueResponse.class

            │           ├── GetUserClaimValues.class

            │           ├── GetUserClaimValuesForClaims.class

            │           ├── GetUserClaimValuesForClaimsResponse.class

            │           ├── GetUserClaimValuesResponse.class

            │           ├── GetUserId.class

            │           ├── GetUserIdResponse.class

            │           ├── GetUserList.class

            │           ├── GetUserListOfRole.class

            │           ├── GetUserListOfRoleResponse.class

            │           ├── GetUserListResponse.class

            │           ├── IsExistingRole.class

            │           ├── IsExistingRoleResponse.class

            │           ├── IsExistingUser.class

            │           ├── IsExistingUserResponse.class

            │           ├── IsReadOnly.class

            │           ├── IsReadOnlyResponse.class

            │           ├── ListUsers.class

            │           ├── ListUsersResponse.class

            │           ├── ObjectFactory.class

            │           ├── RemoteUserStoreManagerService.class

            │           ├── RemoteUserStoreManagerServicePortType.class

            │           ├── RemoteUserStoreManagerServiceUserStoreException.class

            │           ├── RemoteUserStoreManagerServiceUserStoreException_Exception.class

            │           ├── SetUserClaimValue.class

            │           ├── SetUserClaimValues.class

            │           ├── UpdateCredential.class

            │           ├── UpdateCredentialByAdmin.class

            │           ├── UpdateRoleListOfUser.class

            │           ├── UpdateRoleName.class

            │           ├── UpdateUserListOfRole.class

            │           ├── dao

            │           │   └── xsd

            │           │       ├── ClaimDTO.class

            │           │       ├── ObjectFactory.class

            │           │       ├── PermissionDTO.class

            │           │       └── package-info.class

            │           └── package-info.class

            └── user

                ├── api

                │   └── xsd

                │       ├── ObjectFactory.class

                │       ├── RealmConfiguration.class

                │       ├── Tenant.class

                │       ├── UserStoreException.class

                │       └── package-info.class

                ├── core

                │   ├── tenant

                │   │   └── xsd

                │   │       ├── ObjectFactory.class

                │   │       ├── Tenant.class

                │   │       └── package-info.class

                │   └── xsd

                │       ├── ObjectFactory.class

                │       ├── UserStoreException.class

                │       └── package-info.class

                └── mgt

                    └── common

                        └── xsd

                            ├── ClaimValue.class

                            ├── ObjectFactory.class

                            └── package-info.class

18 directories, 81 files