#!/bin/sh
#
# setup DB2 JDBC stuff:
#
export LIBPATH=/usr/lpp/db2810/jcc/lib:$LIBPATH
#---------------------------------------------
export ID=$1
export ACTION=$2
export JMXPORT=$3
#
export CATALINA_HOME=/var/tomcat$ID
export CATALINA_BASE=$CATALINA_HOME
export JAVA_HOME="/usr/lpp/java/J6.0_64"
#export JAVA_OPTS=" -Xmx256M  -Xshareclasses:name=RaboDefaultCache,verbose,groupAccess -Xscmx100M "
export JAVA_OPTS=" -Xmx256M  "
if [ $ACTION != stop ]
then
   echo "using JMX port $JMXPORT"
   export JAVA_OPTS="$JAVA_OPTS  -Djava.security.auth.login.config=/var/tomcat$ID/conf/jaas.config \
   -Ddb2.jcc.propertiesFile=/var/tomcat$ID/conf/db2.jcc.properties \
   -Dcom.sun.management.jmxremote.port=$JMXPORT \
   -Dcom.sun.management.jmxremote.ssl=false \
   -Dcom.sun.management.jmxremote.authenticate=true \
   -Dcom.sun.management.jmxremote.password.file=/var/tomcat$ID/conf/jmxremote.password \
   -Dcom.sun.management.jmxremote.access.file=/var/tomcat$ID/conf/jmxremote.access"
fi
#
umask 007
echo "Starting tomcat.sh with CATALINA_BASE=$CATALINA_BASE and ACTION=$ACTION"
. $CATALINA_HOME/bin/catalina.sh $ACTION

Installing JSPWiki#

Basically the same procedure

• download JSPWiki
• unzip it
• binary upload to tomcat's webapp directory (do not just drop the warfile !)
• customize your jspwiki.properties (and optionally web.xml and jspwiki.policy)

Authentication (and authorization) against SAF #

You probably don't want to run production with the default userdatabase.xml / groupdatabase.xml.
So here are some options to use your SAF security system (RACF, ACF2, TopSecret).

Tomcat realm#

Attached you will find a RACFRealm implementation.
This can be used when you have configured Container Managed Authentication.

Just drop this jar file in tomcat's lib directory and configure the following (example) in your server.xml:

    <Resource name="RACFDatabase" auth="Container"
	      type="nl.rabobank.hdw.tomcat.realm.RACFRealm"
	      factory="nl.rabobank.hdw.tomcat.realm.RACFRealmFactory"
	      description="RACF database"/>
	      
    <Realm className="nl.rabobank.hdw.tomcat.realm.RACFRealm"/>
	      

Recycle tomcat and fire up the tomcat manager application, you should be prompted (Basic Authentication) for your RACF Userid/password.

If you want to use this for JSPWiki, simply enable Container Managed Authentication in the web.xml (see the web.xml for instructions)

There is one big disadvantage of this way of authentication, and that is that you don't get useful error messages back. In our shop we had complaints from people that could not login because of expired passwords or revoked userids and during their login attempt they were not told so. (the JAAS login module has a solution for this, skip to the next paragraph)

JAAS Login module#

The JAAS login module is just what it says. It's an implementation of the javax.security.auth.spi.LoginModule.

To use it in JSPWiki :

• drop the attached racfloginmodule in tomcat's lib directory
• configure this in jspwiki.properties:

jspwiki.loginModule.class = nl.rabobank.hdw.auth.login.RACFLoginModule

• do not use Container Managed Authentication in this case

That's it, recycle your tomcat and login

Pit falls#

Assuming ASCII#

Some Java applications make the false assumption that the default encoding is ASCII, and those don't run correctly on the mainframe.

So when doing IO (files, sockets) think about what the encoding is for the data you are writing/reading :

String encoding = "ISO8859-1";
String fileName = "/tmp/myWonderfulFile";
//
// reading :
BufferedReader in = new BufferedReader(new InputStreamReader(new FileInputStream(new File(fileName)), encoding));
//
// writing :
BufferedWriter out = new BufferedWriter(new OutputStreamWriter(new FileOutputStream(new File(fileName)), encoding));

// Specify an encoding when using the getBytes method to convert a String to a ByteArray:

byte myBytes = myString.getBytes("8859_1");

// Also specify an encoding when creating a String from a ByteArray:

String myString = new String(myBytes, "8859_1"); 

Shell script files in DOS format#

If your shell scripts are in DOS format (instead of Unix format) they don't run.
The easiest way to check this is use your favorite Editor (UltraEdit or something else) and convert them to Unix format.
You can also check it with the hexdump command:

metskem@xat1:/usr/local/tomcat/bin>hexdump version.sh | grep '0d 15'

You can strip off these hex'15' chars with (example) :

cat version.sh | tr -d '\r' > versionNew.sh