Page History

This is how I do it. It does require additional machine resources, as I prefer to create a server per application which provides for better application isolation and turning capabilities.

I have created scripts to do all of this, but it can be equally done via the Administration Console. Archiva works fine with the default settings of "Multiple Classloaders" and either "Parent First" or "Parent Last". Do you do not need to set up a Custom Classloader to cater for the additional jars that Tomcat is missing.

The one major issue that I had was, that no matter what, I could not get Archiva to work with the supplied Apache Derby database - nor could I get it to use a different one (I was not going to update the WebSphere supplied ones directly). So, in the end I used a DB2 database. I've used both a shared DB2 database (used by other apps) and a single database just for Archiva.

1. Create a Server to host Archiva1. Setup as normal.
2. Add a custom property to the Web Container.

Application Servers > <app server> > Web Container Settings > Web Container > Custom Properties

...

Name: com.ibm.ws.webcontainer.invokefilterscompatibility
Value: true
Description: Turn on filter support.

1.2 Create a Virtual Host.
1.2.1 Create a Virtual Host Alias.
1.2.2 Set the Web Container Default Virtual Host name to the appropriate value.
1.3 Create a JAAS entry for the Database User.
1.3.1 Set a WebSphere variable "DB2UNIVERSAL_JDBC_DRIVER_PATH" to where DB2 is installed, eg "/opt/IBM/db2/V9.7/java" (DB2 9.7 on AIX).
1.3.2 Create the DB2 Universal Driver Database Provider.
1.3.3 Create the Archiva Data Source (jdbc/archiva).
1.3.4 Create the Users Data Source (jdbc/users).
1.3.5 Note: Both data sources can share the same database.
1.4 Create the Mail Session (mail/Session). Using the existing built in provider is fine.
1.5 Create a generic JVM property and set it to: "-Dappserver.home=/archiva -Dappserver.base=/archiva". Adjust your path as necessary. Both should be set to the same value.
1.6 Save and Sync the changes.

This was tested on WAS 6.1.0.15 under AIX 5.3 TL6 (and WAS 6.1.0.19 and AIX 5.3 TL8, 10 and 11).