Enterprise Integration for Beginners

Audit logs provide very useful information related to the users who has tried to access the server. By default, most of the WSO2 carbon based products (ESB, APIM, DSS) have not enabled this logging. In production environments, it is always better to enable audit logs due to various reasons. All you need to do is add the following section to log4j.properties file which resides in <CARBON_HOME>/repository/conf directory. # Configure audit log for auditing purposes log4j.logger.AUDIT_LOG=INFO, AUDIT_LOGFILE log4j.appender.AUDIT_LOGFILE=org.apache.log4j.DailyRollingFileAppender log4j.appender.AUDIT_LOGFILE.File=${carbon.home}/repository/logs/audit.log log4j.appender.AUDIT_LOGFILE.Append=true log4j.appender.AUDIT_LOGFILE.layout=org.wso2.carbon.utils.logging.TenantAwarePatternLayout log4j.appender.AUDIT_LOGFILE.layout.ConversionPattern=[%d] %P%5p - %x %m %n log4j.appender.AUDIT_LOGFILE.layout.TenantPattern=%U%@%D [%T] [%S] log4j.appender.AUDIT_LOGFILE.threshold=INFO log4j....

Some important Git commands for branching with remotes and upstream projects First create a fork from an existing repository on wso2 repo https://github.com/wso2 Then create a cloned repository in your local machine from that forked repo. Replace the URL with your own repo URL. git clone https://github.com/chanakaudaya/carbon-mediation.git Now add upstream repositories for your local clones repository.This should be the upstream project which you have forked from. git remote add upstream https://github.com/wso2/carbon-mediation.git You can remove an upstream if you needed. git remote rm upstream Now you can see all the available branches in your git metadata repository. Here you need to keep in mind that only metadata available for all the branches except the master (which is the local branch created by default) git branch -a * master  remotes/origin/HEAD -> origin/master  remotes/origin/master  remotes/origin/release-2.1.3-wso...

CREATE Clone an existing repository $ git clone ssh://user@domain.com/repo.git Create a new local repository $ git init LOCAL CHANGES Changed files in your working directory $ git status Changes to tracked files $ git diff Add all current changes to the next commit $ git add . Add some changes in <file> to the next commit $ git add -p <file> Commit all local changes in tracked files $ git commit -a Commit previously staged changes $ git commit Change the last commit Don‘t amend published commits! $ git commit --amend COMMIT HISTORY Show all commits, starting with newest $ git log Show changes over time for a specific file $ git log -p <file> Who changed what and when in <file> $ git blame <file> BRANCHES & TAGS List all existing branches $ git branch Switch HEAD branch $ git checkout <branch> Create a new branch based on your current HEAD $ git branch <new-branch> Create a new tracking branch based on ...

GIT is one of the heavily used version control systems in the software industry. In this blog post, I am covering the fundamental concepts of GIT vcs for a beginner level user. create a new repository create a new directory, open it and perform a git init to create a new git repository. checkout a repository create a working copy of a local repository by running the command git clone /path/to/repository when using a remote server, your command will be git clone username@host:/path/to/repository workflow your local repository consists of three "trees" maintained by git. the first one is your Working Directory which holds the actual files. the second one is the Index which acts as a staging area and finally the HEAD which points to the last commit you've made. add & commit You can propose changes (add it to the Index) using git add <filename> git add * This is the first step in the basic git workflow. To actua...

Here are some resources which you can use to learn about implementing rule based solutions using WSO2 products stack. Writing Business rules with WSO2 Carbon platform http://www.dimuthu.org/blog/2010/01/07/writing-business-rules-in-wso2-carbon-platform/ Samples available at WSO2 BRS documentation https://docs.wso2.com/display/BRS210/Samples Integrating business rules and the architecture of rules component http://wso2.com/library/articles/2012/12/bringing-business-rules-soa/ Integrate business rules with WSO2 ESB and WSO2 BRS http://wso2.com/library/articles/2011/04/integrate-rules-soa/ Integrate business rules with WSO2 BPS and WSO2BRS http://wso2.com/library/articles/2011/05/integrate-business-rules-bpel/ Complex event processing and business rules integrations with SOA http://wso2.com/library/articles/2011/07/complex-event-processing-business-rule-management-soa/ Developing business rule services with WSO2 Developer Studio http://wso2.com/library/ar...

Hers is a great web site which provides lot of tutorials on network level commands and use cases. http://www.tecmint.com/20-netstat-commands-for-linux-network-management/ http://www.tecmint.com/35-practical-examples-of-linux-find-command/ http://www.tecmint.com/12-tcpdump-commands-a-network-sniffer-tool/

tcpdump  is a most powerful and widely used command-line packets sniffer or package analyzer tool which is used to capture or filter  TCP/IP  packets that received or transferred over a network on a specific interface. It is available under most of the  Linux/Unix  based operating systems. tcpdump also gives us a option to save captured packets in a file for future analysis. It saves the file in a  pcap  format, that can be viewed by tcpdump command or a open source GUI based tool called  Wireshark (Network Protocol Analyzier)  that reads tcpdump  pcap  format files. How to Install tcpdump in Linux Many of Linux distributions already shipped with  tcpdump  tool, if in case you don’t have it on systems, you can install it using following Yum command. # yum install tcpdump Once  tcpdump  tool is installed on systems, you can continue to browse following commands with their examples. 1. Capture Packets f...