...
There is an admin user named "casdev" defined in every Sandbox . There is a single universal password defined for this user (get it from another developer). Because this user is so well known, it is a bad practice to expose the VM to other machines (by giving it "bridged" access to the network). The casdev user is typically OS. Yes, the name comes from designing the Sandbox first to develop CAS, but there was no reason to rename a perfectly good userid. Casdev user is the owner of all the directories used by the development tools or the running application. The Sandbox is not a place to test file security.
Yes, the Sandbox was originally created for CAS development, but it works with other projects and there was no need to rename the user.
If you launch the VirtualBox application you will see a management console. It displays the Virtual Machines (VMs) that you already have and provides a Wizard for creating new VMs, typically by running the OS installer CD image for Windows or a Linux distribution. If you ask it to start an existing VM, VirtualBox creates a simulation of a full personal computer and even runs a power up BIOS. It then boots from the virtual hard disk image or from the virtual CD image.
After installing a new OS, you can mount a virtual CD on the virtual machine and install Linux or Windows Guest VM device drivers. These drivers know about the VM environment, they provide more flexible screen management, and the ability to cut text in the host operating system and then paste it into an application running on the VM (or the reverse). VirtualBox is slowly working on the ability to drag and drop files between the host and the VMs.
A specific restriction on VirtualBox is that the files that it creates to represent the VM and its hard disk are configured with fully qualified path locations, and they contain references to LAN adapters and audio cards on the host machine. They cannot simply be copied from one place to another without fixing this configuration. You can edit the XML in the *.vbox XML file, or you can use the VM clone function to get VirtualBox to make a copy of the file in a new location, or you can Export and then Import the VM on another system.on SandboxData and must have at least write privileges to any directory used during execution (/var/log/jbossas/standalone for example). Because JBoss runs from Eclipse interactively instead of as a service, there is no service account for JBoss or Tomcat or the applications. Casdev runs everything.
Once you have VirtualBox installed, the next step is to install a Sandbox VM.
Virtual Machines are an advanced feature, and people who use them need the ability to specify some advanced options. For example, the host computer can have more than one LAN adapter. One LAN adapter could be connected to the public internet, while the second adapter would be connected to a "lab" network that only includes in one room belonging to your group. When you define a VM, you need to configure its virtual LAN adapter. It could be entirely imaginary and exist only inside your machine, or it could be "connected" to one of the two real LANs. Is it going to be connected to the Internet or to the Lab network? The VirtualBox configuration tool allows you to make the choice.
Now I want to give you a copy of this VM. Your machine may also have two LAN adapters connected to the same two networks, but your machine will not be identical to my original machine. Not only might you have different hardware, but I may be running Windows and you might be running a Mac, so everything has different names. There is no way to create a VirtualBox or any other software that is smart enough on its own to automatically reconfigure the VM. A person is going to have to rename and reconfigure "dangling" devices that on the new machine no longer connect to hardware features that are identical to those on the original machine.
A VirtualBox VM is a directory on disk with an XML configuration file with an extension of *.vbox. You can try to copy the directory from one machine to another, but VirtualBox is not designed to make this easy or reliable. For example, the *.vbox file contains an explicit fully qualified path reference to any *.iso CD/DVD images that were ever used by the machine, even if they are not currently mounted in the drive. Move the VM directory to another computer that does not have an identical *.iso file in the exact same place, and VirtualBox will complain about the VM being broken.
The Sandbox is distributed as a Exported *.ova file. This is an open standard form of zip file that contains both the machine configuration and the disk image. It can be loaded into VirtualBox (or VMWare for that matter) to create the virtual machine. During installation, or any time before you start the VM, you may need to configure features that are potentially dependent on your local machine configuration. VirtualBox has a feature called "Shared Directory" that allows the host operating system to share one of its directories with the VM (like a network share, but implemented without the network). When the distribution was built, the shared directory was "D:\sandbox", but you may want to turn this off (it is a convenience) or change the host directory path, especially if you do not have a D: drive or are not running Windows on your host computer.
...