Create new branch in GitHub

Note: OS Windows
Way 1:
Create new branch from the current branch and automatically switch to it.
$ git checkout -b <branch_name>

Way 2:
1. Create a new branch on the repository
$ git branch <branch_name>
2. Switch to the new branch from current branch.
$ git checkout <branch_name>

Way 3:
1. Create new branch and can specify a different branch which want to create the new branch.
$ git checkout -b <branch_name> <branch-name_which_creates_the_new_branch>

List all the branches in the repository
$ git branch

Create new repository and add existing project to GitHub in command line

Note: OS Windows
1. Create new repository on GitHub. Do not add README and gitignore files, can add it after push the project to GitHub.

2. Open Git Bash.
3. Change the current working directory to your local project.

4. Initialize the local folder as a git repository.
$ git init
5. Add file to the local repository(Stages) to first commit.(To unstage a file, use 'git reset HEAD YOUR-FILE')
$ git add .
6. Commit files staged in the local repository.
$ git commit -m "First commit"
7. Copy the remote repository URL on GitHub.
8. Add/set the URL for remote repository
$ git remote add origin <copied remote repository URL>
(Optional : To verify remote URL - $ git remote -v)
9. Push changes.
$ git push origin master

Reference:
[1] https://help.github.com/en/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line

Adding multiple folders to Git

Use below command (in git bash) for add multiple folders to Git.

$ git add -A 

Then can commit changes and push it to the repository.

Find the process running on specific port

On Windows cmd:

Syntax : netstat<space>-ano<space>|<space>find<space>":<port>"

When run the command related to the port 8006 the output will give as below,
Ex:
C:\Users\hal>netstat -ano | find ":8006"
  TCP    127.0.0.1:8006         0.0.0.0:0              LISTENING       5380

Related to the example, "5380" is the process id(PID), then can check the PID through the Task Manager.

Maven build failed with "Fatal error compiling: invalid target release: 1.8 -> [Help 1]"

The below build failed error popped-up  when I try to build (use mvn clean install) the project with Maven.

Error log:

INFO] ------------------------------------------------------------------------
INFO] BUILD FAILURE
INFO] ------------------------------------------------------------------------
INFO] Total time: 3.390 s
INFO] Finished at: 2017-12-09T16:33:24+05:30
INFO] Final Memory: 9M/150M
INFO] ------------------------------------------------------------------------
ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2
:compile (default-compile) on project dpc-portal: Fatal error compiling: invalid
 target release: 1.8 -> [Help 1]
ERROR]

The reason was, I set JAVA_HOME to the JDK 1.7 (as in below image) but try to build using JDK 1.8. So after change the JAVA_HOME to JDK 1.8 version, project was built successfully.

Reference:
https://stackoverflow.com/questions/28291691/fatal-error-compiling-invalid-target-release-1-8-help-1

Enable Wire Logs in WSO2 ESB

In Some situations need to check the incoming(to ESB) or outgoing(from ESB) HTTP headers and the messages. The Wire log functionality is there to handle this requirement. Main underlying transport mechanism of ESB is Passthrough HTTP Transport which handles the HTTP and HTTPS messages. Hence, it can enable wire logs for Passthrough HTTP Transport as below.

WSO2 ESB 4.7.0 or higher versions.

1. Open log4j.properties file.

log4j.properties file is located in <EBB_HOME>/repository/conf directory.

2. Un-comment the following entry.

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

3. Save the file and restart the server to affect the changes.

In the older versions, it is bit different than the new versions.

For ESB 4.6.0 :

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

For ESB 4.5.1 or previous versions :

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

To see HTTP headers and messages of Callout mediator/MessageProcessor.

1. Open log4j.properties file.

2. Un-comment the following two entries.

log4j.logger.httpclient.wire.header=DEBUG

log4j.logger.httpclient.wire.content=DEBUG

3. Save the file and restart the server to affect the changes.

NOTE: Wire logs should enable only for a troubleshooting purposes, not recommended for the systems in the production environment.

Changing User Passwords In WSO2 ESB.

In this blog, I will explain the way to change the password [1] of the WSO2 ESB (or User Passwords in the Carbon Database). Here I used ESB 4.9.0 version.

What you need to do is run the chpasswd script inside the <PRODUCT_HOME>/bin/ directory.
For an example, I need to change the admin password. So I pass the "username" command line argument also. If we do not provide these as command line arguments, it will be prompted for it during the execution time.

These are the steps you need to follow.

1. Extract the fresh ESB 4.9.0 instance.
2. Start the server.
3. Shutdown the server.
4. Run the below command and set the new password.

• For Linux: ./chpasswd.sh --username "admin" --db-url "jdbc:h2:repository/database/WSO2CARBON_DB"
• For Windows: chpasswd.bat --username "admin" --db-url "jdbc:h2:repository/database/WSO2CARBON_DB"

5. Start the server.
6. Login from the new password and it will log you into the Management Console.

Reference:

[1] https://docs.wso2.com/display/Carbon440/Changing+User+Passwords+in+the+Carbon+Database