Tuesday May 15, 2007
Tuesday May 15, 2007
Tuesday Jan 09, 2007
Got more blogs? More blogs!
Saturday May 06, 2006
IIW2006 Pictures posted[Read More]
Tuesday May 02, 2006
Here are some pictures that I took at Bio-IT World 2006[Read More]
Wednesday Apr 19, 2006
Apparently, the traffic generated by various blogs (including this one) have overwhelmed the web server at my school and caused it to crash periodically. So, I had to take the content off-line to avoid service interruptions. I didn't know how much traffic this has generated and I apologize to the web server's sys admin for all the trouble.
Anyone has any recommendation on a much better Gallery hosting site for a reasonable or low cost? If I have the time, I would prefer to get something ready for JavaOne 2006.
Thursday Dec 01, 2005
I get this question so many times that I believe I should publish it here instead! ;)
* For a quick and dirty workaround, you can disable security manager by removing reference to server.policy in domain.xml. See link
* Here is the proper way to configure the security policy: See link
* If you want to override the default permissions through code instead of configuration, here is one way. See link
* For a quick and dirty workaround, you can disable security manager by removing reference to server.policy in domain.xml. See link
* Here is the proper way to configure the security policy: See link
* If you want to override the default permissions through code instead of configuration, here is one way. See link
Thursday Jun 30, 2005
Today's NetBEAMS demo (see pictures) was successful and flawless. Although one of the team member had to ran to a local Safeway to get ice at the last moment, we were able to get everything in place before the keynote. Some people came to us after the keynote and said that the demo was excellent. Thanks! This certainly was the best JavaOne experience that I ever had! :)
I certainly had a lot of fun taking photos that documented the whole experience with over 200+ posted pictures. I also learned how to better handle my camera and lenses for the low-light indoor environment. One thing that I miss is a 70-200 mm lense for up close portrait shots. Even without the telephoto zoom lense, I was able to "foot zoom" to get most of the shots that I wanted. ;)
Now that it is all done, I would like to wish you all a good 4th of July weekend. I'll be off for a week to recover all the lost of sleep that I went through this week.
I certainly had a lot of fun taking photos that documented the whole experience with over 200+ posted pictures. I also learned how to better handle my camera and lenses for the low-light indoor environment. One thing that I miss is a 70-200 mm lense for up close portrait shots. Even without the telephoto zoom lense, I was able to "foot zoom" to get most of the shots that I wanted. ;)
Now that it is all done, I would like to wish you all a good 4th of July weekend. I'll be off for a week to recover all the lost of sleep that I went through this week.
Wednesday Jun 29, 2005
Today is the demo setup day. I uploaded some back stage shots during the setup. Everything looks good for tomorrow's kenote demo. Make sure you drop by the keynote on Thursday.
In addition to the back stage shots, I also took some pictures in the pavilion. There are a few interesting shots. I like the "gone fishing" note.
In addition to the back stage shots, I also took some pictures in the pavilion. There are a few interesting shots. I like the "gone fishing" note.
Tuesday Jun 28, 2005
Today is the Duke's Choice Award day. I am proud to present an up close and personal photo collection of Duke's Choice Award ceremony. I am happy that months of volunteering work and weeks of not getting enough sleep finally made this winning project get to where it is today!
Monday Jun 27, 2005
The opening day was a blast. The seabird sensor attracted many visitors. If you haven't seen it, you should drop by booth #527 in the Java.net area to see it live.
In addition, there will be mini talks about NetBEAMS/JDDAC:
Tue: 12:30: Introduction to JDDAC
Tue: 3:00: NetBEAMS Overview
Wed: 1:00: NetBEAMS web site
Wed: 1:30: NetBEAMS Data Store
There are many other mini-talks about other projects on java.net. Drop by to see a schedule of the talks!
For those of you who couldn't attend the conference in person, you can see the pictures I posted. In this post, some of the pictures were taken before the opening, so I could get clean shots without people blocking the views. Once the gates were open, people flooded the general session hall and I was fortunate enough to get some close shots for you.
In addition, there will be mini talks about NetBEAMS/JDDAC:
Tue: 12:30: Introduction to JDDAC
Tue: 3:00: NetBEAMS Overview
Wed: 1:00: NetBEAMS web site
Wed: 1:30: NetBEAMS Data Store
There are many other mini-talks about other projects on java.net. Drop by to see a schedule of the talks!
For those of you who couldn't attend the conference in person, you can see the pictures I posted. In this post, some of the pictures were taken before the opening, so I could get clean shots without people blocking the views. Once the gates were open, people flooded the general session hall and I was fortunate enough to get some close shots for you.
Sunday Jun 26, 2005
Today is the setup day for the pavilion booth. Everything looks great by the time the JDDAC/NetBEAMS team finished for the day. There are still final tasks need to be done on Monday morning. All in all, the booth is ready for show time. Come to check out the demo at booth #527 in the Java.net area.
Monday Feb 21, 2005
They are posted here.
Tuesday Jan 11, 2005
I knew this area is well documented. However, I still had to search through forums to find the missing information. So, to show my appreciation, I wanted to put this quick notes together. This is very rough. Feedbacks are welcome.
Disclaimer: This instruction is provided AS-IS. Try them at your own risk. For support, try online forums, which will be much faster than what I can do.
Background Information:
For VNC, please see http://www.realvnc.com/
For SSH, please see http://www.openssh.com/
Where do I get the software?
For VNC, you can get it from http://www.realvnc.com. If you use Linux, you may already have it. Just do a which command to verify.
For SSH, I assume it is already installed. It is available out-of-box for Solaris 9 or better and Red Hat Linux. If not, go to http://www.openssh.com to download a copy or use package management commands such as apt-get or emerge. For windows client, use PUTTY. See http://www.chiark.greenend.org.uk/~sgtatham/putty/
How do I install VNC?
For VNC, If you download the software from realvnc.com, you can either follow the installation instruction by running the installation script. What I did for Solaris distribution was keeping all files in a user home directory. Make sure you update your PATH environment variable so that the user you want to use for running VNC server have access to it.
How do I configure the VNC Server?
For VNC on RedHat Enterprise Linux 4 beta 2, this is what I did:
* su to root
* Un-comment the following lines in /etc/sysconfig/vncservers
VNCSERVERS="1:myusername"
VNCSERVERARGS[1]="-geometry 800x600"
* su to user you will use for connecting to VNC server
* Run the vncpasswd command to set the password.
* Restart VNC Server. Ex: /etc/init.d/sshd restart
For VNC on Solaris, here is what I did:
* In order for VNC to work correctly with SSH, change AllowTcpForwarding parameter to yes in /etc/ssh/sshd_config. Ex: AllowTcpForwarding yes
* To start VNC server:
o su to the user that has access to VNC software (if you installed in a user home directory) or use a user of your choice.
o Run vncserver -geometry 800x600
How do I establish a SSH tunnel?
Below is the command format that I used to establish a SSH tunnel between my client machien and the SSH server machine. Replace SSH_SERVER with the appropriate host name or IP. Replace USER_NAME with the appropriate user name.
/bin/ssh SSH_SERVER -l USER_NAME -L 5901:localhost:5901 -N -f
The above command will drop to background (due to -f option) and you should have your prompt back. Sometimes you may need to change localhost with an IP address, i.e. 127.0.0.1 If you setup your VNC server other than 5901, adjust this command accordingly. To find out which port your VNC server is open at, see VNC server log in .ssh directory in your user home directory on the server side.
How do I verify that the SSH tunnel is valid?
One way to verify the tunnel is to telnet localhost at 5901 (i.e. telnet localhost 5901). You should see a RFB... line.
What if I am behind a proxy server?
Check with your network administrator for socks proxy server information. SSH can use a socks proxy server. The one that I am using is specific to my environment and therefore it is useless for public sharing at this time. At least I can say that I use -o option to add proxy information.
How to I use VNC over a SSH tunnel?
Just point your VNC client (vncviewer) to localhost:1 or localhost:5901. Then you should be asked to enter a password. If you get an error, check if the tunnel is valid (see above). You can also double check the port number that the VNC server listens (i.e. netstat -a |grep LISTEN). You may also want to make sure that you set a VNC password using vncpasswd command.
What if I want to connect to a VNC server that is within a private net protected by a gateway running SSHD?
SSH can also do forwarding, try the following command:
/bin/ssh SSH_SERVER -l USER_NAME -L 5901:MY_VNC_SERVER_HOST:5901 -N -f
Please note the difference between the earlier ssh command, "localhost" is replaced in the -L option to the IP/host name of your VNC server.
Comments or Suggestions? Please feel free to leave me one!
Background Information:
For VNC, please see http://www.realvnc.com/
For SSH, please see http://www.openssh.com/
Where do I get the software?
For VNC, you can get it from http://www.realvnc.com. If you use Linux, you may already have it. Just do a which command to verify.
For SSH, I assume it is already installed. It is available out-of-box for Solaris 9 or better and Red Hat Linux. If not, go to http://www.openssh.com to download a copy or use package management commands such as apt-get or emerge. For windows client, use PUTTY. See http://www.chiark.greenend.org.uk/~sgtatham/putty/
How do I install VNC?
For VNC, If you download the software from realvnc.com, you can either follow the installation instruction by running the installation script. What I did for Solaris distribution was keeping all files in a user home directory. Make sure you update your PATH environment variable so that the user you want to use for running VNC server have access to it.
How do I configure the VNC Server?
For VNC on RedHat Enterprise Linux 4 beta 2, this is what I did:
* su to root
* Un-comment the following lines in /etc/sysconfig/vncservers
VNCSERVERS="1:myusername"
VNCSERVERARGS[1]="-geometry 800x600"
* su to user you will use for connecting to VNC server
* Run the vncpasswd command to set the password.
* Restart VNC Server. Ex: /etc/init.d/sshd restart
For VNC on Solaris, here is what I did:
* In order for VNC to work correctly with SSH, change AllowTcpForwarding parameter to yes in /etc/ssh/sshd_config. Ex: AllowTcpForwarding yes
* To start VNC server:
o su to the user that has access to VNC software (if you installed in a user home directory) or use a user of your choice.
o Run vncserver -geometry 800x600
How do I establish a SSH tunnel?
Below is the command format that I used to establish a SSH tunnel between my client machien and the SSH server machine. Replace SSH_SERVER with the appropriate host name or IP. Replace USER_NAME with the appropriate user name.
/bin/ssh SSH_SERVER -l USER_NAME -L 5901:localhost:5901 -N -f
The above command will drop to background (due to -f option) and you should have your prompt back. Sometimes you may need to change localhost with an IP address, i.e. 127.0.0.1 If you setup your VNC server other than 5901, adjust this command accordingly. To find out which port your VNC server is open at, see VNC server log in .ssh directory in your user home directory on the server side.
How do I verify that the SSH tunnel is valid?
One way to verify the tunnel is to telnet localhost at 5901 (i.e. telnet localhost 5901). You should see a RFB... line.
What if I am behind a proxy server?
Check with your network administrator for socks proxy server information. SSH can use a socks proxy server. The one that I am using is specific to my environment and therefore it is useless for public sharing at this time. At least I can say that I use -o option to add proxy information.
How to I use VNC over a SSH tunnel?
Just point your VNC client (vncviewer) to localhost:1 or localhost:5901. Then you should be asked to enter a password. If you get an error, check if the tunnel is valid (see above). You can also double check the port number that the VNC server listens (i.e. netstat -a |grep LISTEN). You may also want to make sure that you set a VNC password using vncpasswd command.
What if I want to connect to a VNC server that is within a private net protected by a gateway running SSHD?
SSH can also do forwarding, try the following command:
/bin/ssh SSH_SERVER -l USER_NAME -L 5901:MY_VNC_SERVER_HOST:5901 -N -f
Please note the difference between the earlier ssh command, "localhost" is replaced in the -L option to the IP/host name of your VNC server.
Comments or Suggestions? Please feel free to leave me one!
Wednesday Nov 24, 2004
Here are a few quick manual steps that I figured out when I was trying to setup a Directory Server with minimal configuration on Solaris SPARC. These manual steps were done after a "configure later" option in Java Enterprise System 2005Q1. Please note that you might not need to do these manual steps if you choose to configure during installation.
Disclaimer: The instructions are provided AS-IS and use at your own risk. By following these instructions, you agree not to hold me responsible for any damages you might do as a result of following these instructions. It worked in my environment and therefore provided as a reference. The instructions are based on a beta version of the software and may be outdated when the final version releases. These instructions are not endorse by anyone.
Here are the basic steps:
1. Since I prefer to use the default configuration whenever possible, I made sure /var/mps/serverroot directory exists. If not create it.
2. Configure directory server instance
directoryserver -u 5.2 configure
-u specifies what version of Directory Server format to use.
3. I used the Typical option, kept the default administrator names, provide the correct domain name and supply the passwords when asked. At end of the configuration, you should see the status message showing slapd up and running. You might want to note down the configuration information and keep in a safe place.
4. Configure administration server instance
mpsadmserver configure
Follow the wizard and enter all the information it asks. Note down configuration and keep in a safe place.
5. Check out the default configuration Run the following command to bring the rich client GUI:
/usr/sbin/directoryserver startconsole
In the login pop up window, enter the User ID and password you configured earlier. For the Administration URL, make sure you enter the correct value. The Administration URL should look similar to myhost.mydomain.com:admin_port You should have the host name and domain information. You should see which port was used when Administration Server was configured in step 4. Once you entered the correct information you should see the console load correctly.
Here are misc other commands that you might want to use
/usr/sbin/directoryserver -useversion 5.2 stop-admin
/usr/sbin/directoryserver -useversion 5.2 start-admin
/usr/sbin/directoryserver -useversion 5.2 stop
/usr/sbin/directoryserver -useversion 5.2 start
Another way to do the same things are running the specific scripts (start-admin, stopadmin, start-slapd, stop-slapd, and startconsole) in the directory where you configured your instance of Directory Server and Administration Server for your Directory Server. For troubleshooting, see access and errors logs within the logs directory under the instance directory. (i.e. /var/mps/serverroot/slapd-my_host/logs)
Disclaimer: The instructions are provided AS-IS and use at your own risk. By following these instructions, you agree not to hold me responsible for any damages you might do as a result of following these instructions. It worked in my environment and therefore provided as a reference. The instructions are based on a beta version of the software and may be outdated when the final version releases. These instructions are not endorse by anyone.
Here are the basic steps:
1. Since I prefer to use the default configuration whenever possible, I made sure /var/mps/serverroot directory exists. If not create it.
2. Configure directory server instance
directoryserver -u 5.2 configure
-u specifies what version of Directory Server format to use.
3. I used the Typical option, kept the default administrator names, provide the correct domain name and supply the passwords when asked. At end of the configuration, you should see the status message showing slapd up and running. You might want to note down the configuration information and keep in a safe place.
4. Configure administration server instance
mpsadmserver configure
Follow the wizard and enter all the information it asks. Note down configuration and keep in a safe place.
5. Check out the default configuration Run the following command to bring the rich client GUI:
/usr/sbin/directoryserver startconsole
In the login pop up window, enter the User ID and password you configured earlier. For the Administration URL, make sure you enter the correct value. The Administration URL should look similar to myhost.mydomain.com:admin_port You should have the host name and domain information. You should see which port was used when Administration Server was configured in step 4. Once you entered the correct information you should see the console load correctly.
Here are misc other commands that you might want to use
/usr/sbin/directoryserver -useversion 5.2 stop-admin
/usr/sbin/directoryserver -useversion 5.2 start-admin
/usr/sbin/directoryserver -useversion 5.2 stop
/usr/sbin/directoryserver -useversion 5.2 start
Another way to do the same things are running the specific scripts (start-admin, stopadmin, start-slapd, stop-slapd, and startconsole) in the directory where you configured your instance of Directory Server and Administration Server for your Directory Server. For troubleshooting, see access and errors logs within the logs directory under the instance directory. (i.e. /var/mps/serverroot/slapd-my_host/logs)
Thursday Nov 18, 2004
http://events-at-sun.com/webinars/