Thursday, February 19, 2009

Windows Node Progress

I installed Globus 4.0.8 on the Windows node to avoid the potential 4.0x and 4.2x compatibility issues. Eventually we will have to roll out an upgrade to 4.2x across the grid.

I was able to used the host certificates from staging to start the Windows container. The good thing is, Windows can use the certificates generated by the Linux nodes. Later we will have to solve the issue of generating correct subject names from Windows nodes. Until then, the work around is to initiate the user request on the Linux node and copy the certificates to Windows.

I also installed Apache Tomcat 5.5.27 and Apache Ant 1.7.1 in order to match the versions on staging. When I deployed Globus to Tomcat I received a couple minor errors.

Error 1:
C:\gt4>ant -f share\globus_wsrf_common\tomcat\tomcat.xml redeploySecureTomcat -D
tomcat.dir="C:\Program Files\Apache Software Foundation\Tomcat 5.5"
Unable to locate tools.jar. Expected to find it in C:\Program Files\Java\jre6\li
Buildfile: share\globus_wsrf_common\tomcat\tomcat.xml

The Fix: I copied tools.jar from the JDK directory to JRE directory it was looking for it in. This can also be fixed by changing the JAVA_HOME variable.

Error 2:
[copy] Copying 1 file to C:\Program Files\Apache Software Foundation\Tomcat
[copy] Warning: Could not find file C:\gt4\lib\xalan.jar to copy.
[copy] Copying 50 files to C:\Program Files\Apache Software Foundation\Tomc
at 5.5\webapps\wsrf\WEB-INF\lib

The Fix: I renamed xalan-2.6.jar to xalan.jar

This resulted in a successful deployment of the Globus container to Tomcat.
Total time: 1 second

The next test is to deploy one of Felicia's grid services to the Windows node and verify that it can be called remotely.

No comments: