Enterprise Integration for Beginners

First I want to tell you that this is not a 1 minute tutorial as the “Sams Teach Yourself” series. This is about deploying your next WSO2 server (first server you deploy after following this tutorial) in 1 minute . Enough talking and let me take you straight in to the task. The concepts and the configurations I am describing here can be used in any kind of scalable deployment with WSO2 products. Below is a diagram of a system which we normally see in an enterprise integration project. Here you can see there are 3 set of systems and a number of WSO2 servers in the entire deployment. The generic approach to this kind of deployment is to first do the end to end implementation within the development setup and then move these configurations in to QA and Production systems. When you are installing your QA or production environment, you need to make sure all the things that done within the development setup are there in the production setup in a seamless manner. You d

Installing puppet on red hat linux based system This blog post will guide you through installing puppet as a master/agent configuration in a RedHat Linux based systems. This is nothing other than collecting the important information mentioned in the puppetlabs web site. What I have done is collecting pieces of information which is scettered through the puppet web site with adding my own experiences which I have gathered during setting up on my environment. 1. Choose a Package Source Puppet Labs provides an official package repo at yum.puppetlabs.com. It contains up-to-date packages, and can install Puppet and its prerequisites without requiring any other external repositories. This information applies to RHEL itself, as well as any distributions that maintain binary compatibility with it, including but not limited to CentOS, Scientific Linux, Oracle Linux, and Ascendos. Enabling this repository will let you install Puppet without requiring any other external

1. VirtualBox > Settings > Network > Add (you will get vboxnet0) ifconfig #will show you new interface vboxnet0 2. Shutdown your VM and do: VM's Settings > System > check "Enable I/O APIC." VM's Settings > Network > Adapter 2 > host-only vboxnet0 3. Start VM, on guest run ifconfig and check ip 4. Configuring port forwarding with NAT in your host machine VM's Settings > Network > Adapter 2 > Port forwarding and add a rule and give following values to guest port and host port Host port - 2222 Gurest port - 22 5. Now connect to the VM guest os with ssh using the following command ssh -p 2222 root@localhost