Upgrade across multiple versions

Archived from the Feedback page:

I have fallen behind on my upgrades. Can I go directly from 0.1.0 to 0.1.3 or must I run each individual upgrade? Thanks, CB 05-Aug-2006 07:-5 CDT

The code is set up so that all of the updates you need should be applied incrementally, so upgrading from 0.1.0 to 0.1.3 should work fine. The obligatory caveat is that I've not tried it personally, so it's possible a bug might be lurking in there somewhere, but I've also not heard any bug reports and the code is simple enough that I'm confident you'll be fine. For what it's worth, there were no database schema changes after 0.1.0, so the upgrade process shouldn't actually need to do anything for you other than update your system to register it as 0.1.3. -- Ryan 05-Aug-2006 20:50 PDT

>Upgrade from 0.1.0 to 0.1.3 went fine. Had a bit of a scare because I didn't copy mysql jar file into lib directory, but otherwise fine. Still need to see why I need mysql jar file in WEB-INF/lib as I already have it in shared directory. CB 06-Aug-2006 18:34 PDT

That may be due to the way the file is getting loaded - I'll take a look for the next release, but let me know if you discover anything. -- Ryan

Problems with installation (DB2/400)

Archived from the Feedback page:

I tried to install jamwiki version 0.4.3 on Windows XP with Tomcat 5.5.17 and Java 1.5.0_06-b05. Database backend should be a DB2/400. I added the newest JTOpen Driver (jt400.jar) to the webapp libs. I get the following error after the first installation page:

And i can't find any error logs. There is nothing in the standard error logs of Tomcat. There are tables/files created under the schema/lib in the database. Any idea?

By default errors should print to the Tomcat stdout log - there was nothing in those logs? Alternately you can customize the log location by modifying the /WEB-INF/classes/logging.properties file and updating the org.jamwiki.pattern value. I assume there had to be a failure creating tables during your installation, but I don't have a copy of DB2/400 to test with so I'd need a stack trace from the logs. If you do find something please let me know - you can either upload the log here, or email it to me at removed. Sorry for the trouble! -- Ryan 28-Nov-2006 10:35 PST

The problem was that the tables were not journaled. By default if the schema is created with the operating system command CRTLIB then the tables in this library/schema will not be journaled. If the schema is created with the sql command CREATE SCHEMA then the operating system will create everything for you (journals, journal receiver, ...) and every table created in this schema will be journaled. Everything went fine the moment i created the schema with the sql command. -- Mihael

Thanks, I've added this information to Installation#DB2/400.

Where is my jamwiki.properties?

Moved from FAQ

I've downloaded the latest final version (0.6.3), unzipped it, and there isn't a jamwiki.properties in folder classes. Since I tried setup my Ldap-Connection, I can't login anymore, so I began searching the configuration ...

See Installation#Upgrades and the FAQ. During upgrades you'll need to backup & restore the jamwiki.properties file from your previous installation. -- Ryan 29-Feb-2008 06:45 PST

jamwiki update

Archived from the Feedback page:

Hi Ryan, hi all, I do have a problem with my local jamwiki-installation. After a system-crash I lost my jamwiki-war and all the jamwiki-properties and so on. But I do have a copy of the database-tables. How do I reactivate my jamwiki? Update seems impossible to me. How can I re-use my data? Thanks to all for every tips. Michael Habbert 17-Dec-2007 12:27 PST

I'm not sure if this will work for you, but when I'm testing I do the following:

1. Backup your database data.
2. Delete the JAMWiki database table (make sure you have a backup!)
3. Install a new instance of JAMWiki using the same database settings as your old instance.
4. Shut down JAMWiki.
5. Restore you database from the backup.
6. Restart JAMWiki.

I use that process to make a copy of jamwiki.org on my local machine, and it seems to work well. Hope that helps. -- Ryan 17-Dec-2007 12:57 PST

Hi Ryan, I finally did it. Nearly done but:

-------------
2007-12-20 21:38:34,824 SEVERE: org.jamwiki.model.WikiUser - Unable to retrieve default roles for GROUP_REGISTERED_USER
java.lang.Exception: Failure while executing select * from jam_role where role_name in ( select jam_role_map.role_name from jam_group, 
jam_role_map where jam_group.group_id = jam_role_map.group_id and jam_group.group_name = ? ) 
       at org.jamwiki.db.WikiPreparedStatement.executeQuery(WikiPreparedStatement.java:84)
-------------

So can I fix this by hand? ;-) -- Michael Habbert 20-Dec-2007 12:34 PST

Hi Ryan, I fixed it by hand! After some try and error I did setup a clear new jamwiki-site and transferred the old jam_topic and jam_topic_version tables into the new site. After that I rebuilded the StyleSheets and so ;-) the only thing will be to register again and change the sites with the category-tags so the categories become rebuild. Year!! Puh my last error from system crash is fixed ;-) Thanks. -- Michael Habbert 02-Jan-2008 00:21 PST

Upgrade blurs

Archived from the Feedback page:

I'm new to jamwiki, first of all thank you for that great tool. I'm sure it will help us a lot! Installation of 0.5.1 was plain sailing, but now I don't understand how to upgrade. Neither I can't find the everywhere mentioned UPGRADE.txt nor I know what to do when I'm told to "Remove the old JAMWiki installation" (running tomcat on a SuSE 9.2 box). Does that mean to delete the jamwiki dir tree? fmr 20-Mar-2007 00:20 PST

Documentation is unfortunately not a strong point of this project thus far, but contributions are always welcome. You're right that there isn't an UPGRADE.txt file, so any references should probably be removed. Step-by-step upgrade instructions can be found in the release notes as JAMWiki 0.5.2#Upgrades. "Removing the old installation" means deleting the JAMWiki files in your web application server, although that step isn't 100% necessary - it just avoids problems if (for example) a JAR file was updated and having two versions could produce problems. If you have suggestions as to how to make the upgrade steps clearer please feel free to edit JAMWiki 0.5.2#Upgrades and I'll be sure to use the updated steps for the next release. -- Ryan 20-Mar-2007 21:27 PST