highlylogical.com » Java

At long last…

mikepigg — Wed, 19 Mar 2008 14:58:41 +0000

I have learned why internationalization is abbreviated to ‘i18n’ thanks to Sun’s internationalization documentation. Now if only I knew why there’s so much more moo shu than pancakes…

Tales of a Linux/DB2 Noob

mikepigg — Wed, 27 Feb 2008 20:10:02 +0000

So I tried to install DB2 8.2 on Fedora 8 recently. The install seemed to go smoothly, but then I couldn’t really do anything. Running any DB2 command (like ‘db2′) would give strange errors like:
SQL10007N Message “-1390″ could not be retrieved. �Reason code: “3″.
and
./db2cc: line 26: db2javit: command not found
and
DB2JAVIT : RC = 9501DB2INSTANCE : -2029059916

After searching the web and trying a number of things with no better results, I tried logging in as the db2inst1 user created during installation. Voila! Everything works beautifully. The thing that I was missing for using DB2 commands from other users was adding DB2 environment variables.�The script that does this in a default installation is /home/db2inst1/sqllib/db2profile. Running the following command sets up the DB2 environment:
. /home/db2inst1/sqllib/db2profile

Okay, this is probably a total noob mistake, but if this post helps just one person, it was worth it. �

Setting up OpenLDAP on OS X Leopard

mikepigg — Sat, 09 Feb 2008 17:53:06 +0000

Recently I was asked to look at building a web application that would run on Tomcat and use Active Directory for authentication. Since I didn’t exactly know how to do this, I thought it would be interesting to get an OSS LDAP server up and running on my Mac and try hooking into it with Tomcat. Since I couldn’t find this already on the net, I thought it would be handy to document the process I went through to get this set up.First, you will need to have the following packages installed:- MacPorts- TomcatNow for the step-by-step:Install OpenLDAP from MacPorts

 sudo port install openldap

Copy slapd.conf.default to slapd.conf

cp /opt/local/etc/openldap/slapd.conf.default /opt/local/etc/openldap/slapd.conf

Customize OpenLDAP configuration for Tomcat sample schema

edit /opt/local/etc/openldap/slapd.conf

Add additional schemas needed to support the Tomcat sample:

include		/opt/local/etc/openldap/schema/cosine.schemainclude		/opt/local/etc/openldap/schema/inetorgperson.schema

Also set suffix and rootdn as shown in this sample. There’s no need to change the database type, however.Notice that the slapd.conf file defines a location that doesn’t exist for a pidfile and argsfile, so we’ll need to create the directory:

sudo mkdir /opt/local/var/run

Start up OpenLDAP:

sudo /opt/local/libexec/slapd

Check that it’s running:

ps -ef|grep slapd

If it’s not, use -d -1 options on the command line to see what’s causing it to fail.Copy the LDIF sample file shown on the Tomcat page into a text file.Import the sample data:

 ldapadd -x -D "cn=Manager,dc=example,dc=com" -W -f tomcatsample.ldif

Backup Tomcat’s server config

cd tomcat_rootcp conf/server.xml conf/server.xml.backup

Edit the realm definition as shown on the Tomcat page – authentication should not be needed to do LDAP lookups with the default configuration

edit conf/server.xml

Installing WAS 6.1 on Fedora 8

mikepigg — Mon, 14 Jan 2008 15:05:51 +0000

I’ve recently been playing around with Fedora 8 as an environment for installing WAS while I work on certification. There were a couple of glitches that stumped me for a day or so, but since then it’s been working great.

The first problem was related to updates. I could run the launchpad application, but when I tried to run the WAS installer, it would crash and core dump. Eventually I found an article on devloperWorks talking about a similar problem installing DB2. The poster said that an update fixed his problem. Although Fedora was offering 140 updates, I didn’t want to spend the time installing them. I decided to go ahead and do that, and afterwards my core dump problem was fixed.

However, now the installer just quit without doing anything (or even showing an UI) rather than core dumping. A post by Kenny Smith suggested that there were some other packages that needed to be installed as documented in the manuals. I decided to read the installation manuals on the InfoCenter, and followed the instructions for RHEL5. Sure enough, there were four or five packages that were documented as being required that were not installed by default, so I went ahead and installed them. Lo and behold, the installer ran and installed WAS!

I guess the moral of the story is two-fold: 1) Install the updates that the system is offering. 2) Read the manual.