Sun VirtualBox practice 3 - Dev Environment on Ubuntu 9.10

The configurations for my personal Dev Environment on Ubuntu 9.10 are pretty straight forward.

Install Ubuntu 9.10 Server

1. download ubuntu-9.10-server-i386.iso from http://www.ubuntu.com/getubuntu/download-server based on Alternative download options

2. install Ubuntu 9.10 server (guest) on Windows XP hosted Sun Virtualbox 3.1.2

3. select predefined OpenSSH server and Samba file server collection of software on top of the core system as my Dev environment

Install GNOME GUI in Ubuntu 9.10 Server
  sudo apt-get install ubuntu-desktop

  with 'Y' to continue
  after installed Ubuntu desktop
  sudo shutdown -h -P now

Install Netbeans in Ubuntu 9.10

  sudo apt-get install netbeans
  with 'Y' to continue

Install Eclipse in Ubuntu 9.10

  sudo apt-get install eclipse

  with 'Y' to continue

Install Telnet server in Ubuntu 9.10

  sudo apt-get install xinetd telnetd
  with 'Y' to continue
  sudo vi /etc/inetd.conf to add
  telnet stream tcp nowait telnetd /usr/sbin/tcpd /usr/sbin/in.telnetd
  sudo vi /etc/xinet.conf to be
  # Simple configuration file for xinetd
  #
  # Some defaults, and include /etc/xinetd.d/


  defaults
  {


  # Please note that you need a log_type line to be able to use log_on_success
  # and log_on_failure. The default is the following :
  # log_type = SYSLOG daemon info
  instances = 60
  log_type = SYSLOG authpriv
  log_on_success = HOST PID
  log_on_failure = HOST
  cps = 25 30
  }


  includedir /etc/xinetfd.d

  restart xinetd service after the Telnet installation

  sudo /etc/init.d/xinetd restart

More display resolution for Ubuntu 9.10 guest on Sun VirtualBox

  Sun VirtualBox -> Devices -> Install Guest Addtions ...
  sudo sh /media/cdrom/VBoxLinuxAdditions-x86.run
  Full Screen (right Ctrl + F), Seamless Screen (right Ctrl + L) will be available after reboot.

Sun VirtualBox practice 2 - Package Software Testing Automation

Few years ago I was designing, programming some install package software (InstallShield, NSIS and etc based) with the silent install/uninstall feature enabled for few software projects.
A PERL script was also developed for testing the daily build based package software testing automation. The auotmation was configured on a dediccated server and doing install and uninstall on the server everyday. Sometimes, there was a package software defect, then after the analyzing, the defect could easy fixed, which is the purpose of the package software testing automation. But afterwards the server clean up toke some time.
Now using Sun VirtualBox’s VBOXManage command line utility and pre configured clean, fresh Sun VirtualBox guest OS (with snapshot).
It’s a doable solution to design and develop package software testing automation:
1. Use VBOXManage to get a pre configured clean, fresh Platform
2. Attached the the package software to the VirtualBox sharefolder
3. Invoke the silent install/uninstall 
…

Sun VirtualBox practice 1 - A Portable Personal Lab

I use to store my Personal Virtual Lab carrying with VMware workstation edition based guest OS (such as, Windows, Linux and Solaris) on an external hard drive.

With a simple customized customize VMware workstation guest OS Configuration file to the external hard drive, my Personal Lab was able to be easily plugged in and worked on different hosting OS (with same OS type), for instance, simple switch from one Windows XP desktop to one Windows XP laptop (both of hosting OS have the same VMWare workstation edition installed already) and continue your works in the Personal Lab.

This approach has been working with me for many years, did the great job and especially did save my lot of time. Sometimes, you might need a quick Lab testing based on an existing environment (for instance, Windows 2003 SE with SQL 2005), with this approach and VW snapshot, there will be no extra environment setting up time at all.

With the free PUEL (Personal Use and Evaluation License) Sun VirtualBox software, a similar approach could be configured to achieve plugging in and working on a different hosting OS (with same OS type) as below:

1. Open Sun Virtual Box, Sun Virtual Box -> File -> Preferences -> General, change the Default Hard Dish Folder and Default Machine Folder to the external hard drive, for instance,

Note: this configuration should be done on all of hosting OS

2. During Create New Virtual Machine, Save the Virtual Disk Location to the external hard drive, for instance,

3. Always copy the latest version of %UserProfile%\.VirtualBox (VirtualBox.xml is under .VirtualBox folder) to the external hard drive when finish works in the Personal Lab.
Note: this is the key to achieve our goal -- portable Sun VirtualBox guest OS on different hosting OS.
This latest version of .VirtualBox folder (with associated VirtualBox.xml) need be copied back into your new hosting OS under %UserProfile% folder if you do want to switch and also assuming the same version of Sun VirtualBox installed already on the new hosting OS.
4. If Enable Network Adapter is checked, Select an associated Network by simple picking the right one from the drop down list.

Note: All of VirtualBox guest OS should be Power Off.

Enterprise Architecture Practice 2 - Handle bilingual in Casewise diagram

After presented the migration Excel format BFM (English version) into Casewise repository with Casewise diagrams, one more requirement came out from the customer, which required to combine their existing separated Excel format BFM (English version) and BFM (French version) into one Casewise model with bilingual (English and French) feature model diagrams.

They really didn’t want to maintain two separated language versions of BFM in Casewise with lots of time costing between two language version sync.
Casewise does have an out of box feature - Multi-Language Manager, which helps create different language versions of the models.

For instance, if you do have English version Casewise model, and want to have a translated French verison Casewise model. By using Casewise Multi-Language Manager, end up getting 2 models – one English version model and one French version model

Obviously, Casewise Multi-Language Manager wouldn’t fit the customer’s requirement one Casewise model diagram with bilingual (English and French) feature.
After a little bit digging and practicing Casewise Out-Of-Box features (region and properties), I figured out that the best practice approach as below, which fits the customer’s one Casewise model diagram with bilingual (English and French) feature.

1. Based on the migrated English version BFM
2. Add more property types for User Defined (BFM Business Services, BFM L1 Element, BFM L2 Element, BFM Competency), such as, Name(Fr), Description(Fr), and etc
3. Casewise AutoModeler imports Excel format BFM (French version) into Casewise repository
4. In Pallatte Properties use regions for BFM Business Services, BFM L1 Element, BFM L2 Element, BFM Competency
5. End user could esaily switch between the different region displays in Pallatte Properties for different language in the diagram. By default, it was configured to French language.

Enterprise Architecture Practice 1 - Casewise as an EA tool

Has been involving to an Enterprise Architecture Practice project for a well-known montreal based financial institution since Aug 26, 2009, and so far has made some significant progresses with deliverables.

Casewise Corporate Modeler Suite uses as an EA tool for Enterprise Architecture Practice project.
Excel format Business Function Model into Casewise repository migration:

1. Casewise AutoModeler imports Excel data into Casewise repository

2. Taxonomic sense will give some inspirations for User Define (Object Type, Association Type, Property Type ans etc)

3. Mapping BFM Business Services, BFM L2 Element, BFM L1 Element, BFM Competency between Excel and Repository

4. Each of BFM Business Services should be offered by one BFM L2 Element, and could be used by many of BFM L2 Elements

5. Property Type handles User Define BFM L1 Element Level, EA Phase, Element Type and etc

Customized BI solution enabled for Casewise

A Customized BI (Business Intelligence) solution (a Casewise complimentary solution) enabled for Casewise.
For example,
Casewise with customized BI solution enable (No any layer limitation, real time reporting)

Software Change & Config Mgmt enabled for Temenos T24 (Banking Software)

Temenos T24 customization with (such as, T24 screen, T24 routine) source code version control, compilation and deployment automation.
For example,
Software Change & Config Mgmt enabled for Temenos T24 (Banking Software)