Page History

...

Archiva has been used with DB2 V8.2, V9.5 and V9.7.

Archiva's reporting functions require some large tables (in terms of the size of an individual row) to be created. In DB2, these rows/table definitions must fit within a Page. The default page size for DB2 is 4K. I've found that a 32K page size is required for Archiva V1.3. If you do not have a DB2 database with a 32K page size available, you will need to create one. Here is a sample script to create one:

...

db2 -tvf create-archiva.sql

Three additional scripts, reorg-archiva.sh, runstats-archiva.sh and count-archiva.sql have also been provided to assist in normal DBA work.

Archiva on WebSphere 6.1

Creating and installing Archiva is a now a simple matter of executing the supplied scripts. You will probably need to edit them just to set the appropriate Cell and Node settings. Generally, the variables that need editing are at the top of the scripts.

...

• create-archiva.sh - A shell script to create the Archiva Logical Volume and File System.
• clean-archiva.sh - A shell script to remove the Logical Volume and File System.
• create-archiva.sql - A DB2 SQL file to create a DB2 database with the necessary page size.
• createArchivaServer.py - wsadmin script to create the Archiva Server.
• deleteArchivaServer.py - wsadmin script to delete the Archiva Server.
• installArchiva.py - wsadmin script to install the Archiva Application into the Archiva Server.
• wsadminlib.py - The wsadmin Über library.
• reorg-archiva.sh - DB2 reorg script for the Archiva DB.
• runstats-archiva.sh - DB2 runstats script for the Archiva DB.
• count-archiva.sql - DB2 sql script to count all of the records in the Archiva schema/database.

Additional Setup

The indexing of files can take a large number of files. I have set the number of files for the user to 20,000 (as 10,000 was not enough). Edit /etc/security/limits to change this value.

Please remember that a 64-bit JVM takes about 60% more heap space than a 32-bit JVM does. Size your VM, if using 64-bit, accordingly. I'm using 1Gb (-Xmx1024M) heap, as 512Mb was causing regular heap dumps due to out of memory errors.

Notes

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

...