1 / 18

Creating a Personal Webvoyáge Development Environment

Creating a Personal Webvoyáge Development Environment. Using VMware Chris Delis, CARLI. Why might you need a personal development environment?. Multiple Developer Environment. Fundamental Issue With Multiple Developer Environments.

jacoba
Download Presentation

Creating a Personal Webvoyáge Development Environment

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Creating a Personal Webvoyáge Development Environment Using VMware Chris Delis, CARLI

  2. Why might you need a personal development environment?

  3. Multiple Developer Environment

  4. Fundamental Issue With Multiple Developer Environments One set of files, but more than one set of changes need to be made. E.g., two developers working on separate features which share common files.

  5. Suboptimal “solution” Coordinate efforts by word of mouth (in person, email, etc.) and “take turns” editing the same files.

  6. Suboptimal “solution” Disadvantages: • Slows down development • Difficult to track changes between efforts (who made which changes?)

  7. Solution is source control. Source control software, such as subversion, is designed to help solve these problems. But this solution depends on allowing each developer their own personal development environment.

  8. Where should I create these personal development environments? • On the same server • On your own machine (laptop) using virtualization software (VMware)

  9. On the same server Server Tomcat Tomcat vwebv VxWS

  10. On the same server Advantages: • No additional hardware or software needed • No need to setup additional OS, Tomcat, and Java

  11. On the same server Disadvantages: • Need to modify Tomcat environment for each additional development branch of Webvoyáge • This means the file structure will be different than production (xxxdb/tomcat/vwebv)

  12. On your own machine(VMware) Server Tomcat vwebv VxWS Laptop Tomcat vwebv

  13. On your own machine(VMware) Laptop Server Tomcat Tomcat vwebv vwebv VxWS Laptop Tomcat vwebv

  14. On your own machine Advantages: • File structure can be the exact SAME as production (xxxdb/tomcat/vwebv) • You may restart Tomcat any time you wish without impacting others. (E.g., you may change Tomcat settings, add profiling tools, etc.)

  15. On your own machine (cont’d) Advantages: • Virtual Machines are easy to copy. Only one setup needed; the rest can be imaged. • VMs may also be installed on server (VMware ESX) • Your previous (single) development environment can now become a staging area for production

  16. How to setup master VM image • Install your favorite OS. E.g., Ubuntu 8.04 LTS • Install recent version of Java SDK. E.g., Sun JDK 1.6.xx • Copy (svn checkout) vwebv source files to your new VM. Note: no need to copy any VxWS files! • Configure vwebv to communicate with main “staging” development server (web.xml)

  17. Edit vwebv/context/vwebv/WEB-INF/web.xml <context-param> <param-name>XServiceHost</param-name> <param-value>localhost</param-value> <param-value>staging.server.edu</param-value> <description> The host of the voyager XServices. </description> </context-param>

  18. That’s it! You now have your own development environment where you can create your own branches, merge changes, etc., without impacting other developers. svn copy trunk mybranch svn checkout svn commit svn merge etc.

More Related