Migration guide to Signsoft intelliBO 4.0
Introduction
This migration guide is intended to reduce migration efforts of switching from Signsoft intelliBO 3.7.X to 4.0.X. This guide comprehensively addresses all known issues you might run into. It will give you advice of what and how to change within your application to maintain compatibility with Signsoft intelliBO 4.0.X.
Based on prior experience, we estimate that a migration to Signsoft intelliBO4 will take between a couple of hours to at most two days. However, certain constellations might require a considerable time to accomplish the migration. This migration guide will help you to identify these constellations and resolve them. We recommend you to entirely read this guide before your start the migration process.
This migration guide is based on the assumption that you only switch to Signsoft intelliBO4 without simultaneously altering other parts of your system. We urge you to complete the intelliBO migration before you move on to exchanging other parts of your system. Please consult supportteam@signsoft.com for assistance when you are migrating to Java 5, Bea Weblogic 9 or Oracle 10g.
Why migrate?
The most obvious reason to migrate is the end of life of Signsoft intelliBO3 at the end of 2006. From the first of January 2007 there will be no support and no bug-fixing for any version of Signsoft intelliBO prior to 4.0.
Other, more tempting and less compelling reasons to migrate to Signsoft intelliBO4 comprise:
- JDO2 features, such as customizable fetch groups or PersistenceManager#flush()
- performance improvements in typical application hotspots
- a slimmer exception handling
- a customizable logging based on log4j
- a highperformance second level object cache
- extended JDOQL features such as the instanceof operator
- cast operations in JDOQL filters
- cast operations in Query#addFetchGroupAttribute()
- SQL-fetch-stategies to minimize the number of SQL select statements