- Download open source SOAPUI – https://www.soapui.org/downloads/latest-release.html
- Select “Linux Installer (64-bit)” – Adjust accordingly.
- Click on Download.
- Once it is download, chmod 755 SoapUI-x64-5.2.1.sh
- Then run it: ./SoapUI-x64-5.2.1.sh
- A pop-up will open. Accept all the defaults and follow the wizard to get it installed.
- It will be installed by default under: $HOME/SmartBear/SoapUI-5.2.1/bin/SoapUI-5.2.1
- Select to open it at the end or double click the “SoapUI 5.2.1.desktop” icon at the Desktop.
If you need to add an extra volume storage into an existing VBox VM, you can use VirtualBox for that.
- Stop your VM and go to Virtual Box – Storage
- Select the Controller: SATA and click the green plus icon to add a new disk
- Select the type and size
- Start your instance
Once it is running you have to format and mount the new disk, for this, as root run
fdisk –l or lsblk
This will let you discover the name of the extended volume. In this case it is /dev/sdb
For more information, refer to: https://help.ubuntu.com/community/Gufw
Gufw is a firewall powered by UFW (Uncomplicated Firewall). For an overview of firewalls, please see Firewall.
I took these instructions from: http://ubuntuhandbook.org/index.php/2016/04/enable-ssh-ubuntu-16-04-lts/
To install it, open terminal (Ctrl+Alt+T) or log in Ubuntu server and run command:
sudo apt-get install openssh-server
After that, you should have SSH service enabled in your system, you may check its status by running command:
sudo service ssh status
You may change some settings (e.g., the listening port, and root login permission) by editing the configuration file via command. Otherwise if you are happy with the default settings, you are done!
sudo nano /etc/ssh/sshd_config
Finally apply the changes by restarting or reloading SSH:
sudo service ssh restart
I based these instructions from: http://askubuntu.com/questions/9540/how-do-i-change-the-computer-name
If, for whatever reason you need to change your hostname, as I had to, you need to edit the computer name in two files:
Installing VirtualBox and running your own VBox VMs
In this section we are going to install a headless VirtualBox. I like the idea of keeping it at the command line (i.e. no graphical interface), so that it consumes less resources and also so that it can be easily scripted and automated. Otherwise if you prefer to install a graphical user interface, there are a few options; you can use an x11 server tunnelling though your laptop and simply export the display into your machine. Another option is to use a remote desktop software like VNC or NoMachine.
In order to install a headless version of VirtualBox in RedHat and Fedora distributions follow the next set of instructions:
These instructions were taken from: http://tecadmin.net/install-oracle-virtualbox-on-centos-redhat-and-fedora/#
Add Required Yum Repositories. Firstly you are required to add VirtualBox yum repository in your system. Download repository file from its official site and place it under at /etc/yum.repos.d/virtualbox.repo – First navigate to /etc/yum.repos.d/ directory and get the repo
Similarly, add EPEL yum repository:
Before installing VirtualBox make sure to install all required packages to run VirtualBox like kernel-headers, kernel-devels etc. Use following command to install required packages.
sudo yum install gcc make patch dkms qt libgomp
sudo yum install kernel-headers kernel-devel fontforge binutils glibc-headers glibc-devel
Setup the environment variable KERN_DIR. VirtualBox installation required kernel source code to install required modules. We need to configure environment variable KERN_DIR to which VirtualBox get kernel source code. In my case latest kernel source is available in 2.6.32-642.6.1.el6.x86_64 directory under /usr/src/kernels/ – Make sure you are using correct source path.
Install Oracle VirtualBox now. Use following command to install VirtualBox 5.1 using yum command line tool. It will install latest version of VirtualBox 5.1.x on your system.
sudo yum install VirtualBox-5.1
After installation we need to rebuild kernel modules using following command:
sudo yum install kernel-uek-devel-3.8.13-220.127.116.11.el6uek.x86_64
How to install Virtualbox 5.1 in Ubuntu:
1. The 5.1 release conflicts with the old 5.0 or 4.x releases, so first open terminal (Ctrl+Alt+T) and run command to remove the previous VBox installation (if any):
sudo apt remove virtualbox virtualbox-5.0 virtualbox-4.*
sudo apt-get purge virtualbox*
2. Download Virtualbox 5.1 for your OS (i386=32bit, amd64=64bit):
Double click the deb file and install via Ubuntu Software.
3. For those who want to install VBox 5.1 from official Linux repository and receive future updates via Software Updater. Run the commands below one by one in terminal:
Note: According to your Ubuntu codename, replace xenial with wily, trusty, or precise.
sudo sh -c 'echo "deb http://download.virtualbox.org/virtualbox/debian xenial contrib" >> /etc/apt/sources.list.d/virtualbox.list'
wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -
sudo apt update
sudo apt install virtualbox-5.1
Congratulations!!! That's it.
NOTE: If you are within a proxy, then try:
sudo http_proxy=http://www-proxy.au.oracle.com:80 apt update
sudo http_proxy=http://www-proxy.au.oracle.com:80 apt install virtualbox-5.1
If you want to manage your VMs from within the Host Machine, you can use VBoxManage – See https://www.virtualbox.org/manual/ch08.html for more information. Some useful commands are:
List all loaded VMs
VBoxManage list vms
List all running VMs
VBoxManage list runningvms
VBoxManage list runningvms
List info about a specific guest VM
VBoxManage guestproperty enumerate [VM_Name]
A variation of the latest in order to just get the IP Address:
VBoxManage guestproperty enumerate [VM_Name] | grep IP
VBoxManage guestproperty enumerate "ICS16.3.5_OP" | grep IP
Name: /VirtualBox/GuestInfo/Net/0/V4/IP, value: 10.0.0.50, timestamp: 1476324285478581000, flags:
- Control Running VMs lifecycle:
VBoxManage controlvm <vmname> pause|resume|reset|poweroff|savestate
- Get the complete list of options with:
- In order to start your VM in headless mode:
VBoxManage startvm <vmname> --type headless
- Import a New Appliance:
VBoxManage import [Appliance]
- Authorising certificates:
VBoxManage import Integration_18.104.22.168.0_OTN.ova --vsys 0 --eula accept
- Setting the NIC interface to bridge:
VBoxManage showvminfo [VM Name], e.g. VBoxManage showvminfo Integration_22.214.171.124.0_OTN
See the NIC interface number in use:
VBoxManage modifyvm [VM Name] --nic<1-N> none|null|nat|natnetwork|bridged|intnet|hostonly|generic --cableconnected<1-N> on|off
VBoxManage modifyvm Integration_126.96.36.199.0_OTN --nic1 bridged --cableconnected1 on
When creating your Development environment it is recommended that you move to a Linux platform. This is so that you can make use of the Docker containers, as well as avoiding multiple issues that exist when running some Modules of Node JS, such as socket.io
There are multiple ways you can get access to a Linux environment, even while working on a Windows platform. The recommended way in this guide is by using Oracle VirtualBox.
- Go to VirtualBox website (https://www.virtualbox.org/) and download the latest version. At the moment of writing this document, the latest version is 5.0.16 for Windows x86/amd64
Notice that if using OS X, you can still download a VirtualBox distribution. The main reason why you would still want to do it is because that way you can standardise a single platform among a team members, as well as having the ability to recreate your development environments over and over again, without affecting your host OS (Windows/OSX). For the case of this example, we are going to standardise using Xubuntu.
This section shows you how to use Oracle IaaS in order to create a new OEL environment. For this, it is assumed that you already have access to Oracle IaaS, if not, either go to cloud.oracle.com and request a trial account or contact your local Oracle representative directly.
Oracle VirtualBox allows running a machine image on a virtualisation layer. Given Oracle IaaS is itself a virtualisation layer (Xen based) you cannot simply install VirtualBox on an Oracle IaaS VM and upload your VirtualBox VMs. That won’t work, as you cannot run VirtualBox on top of a Xen based virtualisation.