Difficulties migrating from Tomcat to WebSphere

Hi,

We have an existing instance running on tomcat. We are not moving it
to websphere and have gone through the configuration steps as
outlined in the doc. We have security etc configured in WebSphere so
that we can authenticate and Jazz starts up. However it does not
appear to be seeing our database configuration as evidenced by these
entries in the jazz.log file:

19:42:08,324
INFO uration.OverridablePropertyFileServerConfiguration - Loading
configuration from
"com.ibm.team.repository.common/teamserver.properties".
19:42:09,766 WARN
m.team.fulltext.service.internal.index.IndexConfig - CRJAZ8180E:
Using temporary directory as index location. Please set the
configuration parameter com.ibm.team.fulltext.indexLocation
19:42:09,774 INFO
m.team.fulltext.service.internal.index.IndexConfig - Fulltext Index
Location: /tmp/fulltext_index/
19:42:10,667 INFO
repository.service.internal.rdb.ConnectionFactory - Initial
database connection successful
Db Product Name: Apache Derby
Db Product Version: 10.3.2.2 - (650004)
Db Name/Location: /tmp/apollo-repo

Here are the same entries when starting up with tomcat:

12:19:37,617
  INFO
uration.OverridablePropertyFileServerConfiguration  - Loading
configuration from
"file:///opt/IBM/JazzTeamServer/server/teamserver.properties".
12:19:40,908   INFO
m.team.fulltext.service.internal.index.IndexConfig  - Fulltext Index
Location: workitemindex/fulltext_index/
12:19:42,451   INFO
repository.service.internal.rdb.ConnectionFactory  - Initial
database connection successful
Db Product Name: DB2/LINUX
Db Product Version: SQL09051
Db Name/Location:
//localhost:50001/JAZZ:fullyMaterializeLobData=false;user=xxxxxxxx;password=xxxxxxxx;

Here is the contents of teamserver.profile (XXXX = blanked out for
privacy)

com.ibm.team.repository.user.registry.type=LDAP
com.ibm.team.repository.db.vendor=DB2
com.ibm.team.repository.db.jdbc.location=//localhost\:50001/JAZZ\:fullyMaterializeLobData\=false;user\=db2inst1;password\={password};
com.ibm.team.repository.db.jdbc.password=XXXX
com.ibm.team.repository.db.db2.content.tablespace.location=content_tablespace
com.ibm.team.repository.db.db2.content.tablespace.numpages=250000
com.ibm.team.repository.changeEvent.expirationDefault=1209600
com.ibm.team.repository.ws.allow.admin.access=true
com.ibm.team.repository.web.suppressedPages={"com.ibm.team.repository.web.admin"\:
}
com.ibm.team.repository.web.pageorder={"com.ibm.team.repository.web.admin"\:
,
"com.ibm.team.process.web.projectArea"\:
,"com.ibm.team.process.web.projectAreaList"\:
}
com.ibm.team.repository.changeEvent.expirationByType=com.ibm.team.workitem.WorkItem\:5184000
com.ibm.team.build.BuildResult\:172800
com.ibm.team.repository.changeEvent.expirationByCategory=SystemLog\:259200
com.ibm.team.fulltext.indexLocation=workitemindex
com.ibm.team.repository.ws.allow.identity.assertion=false
com.ibm.team.repository.web.helpuri=http\://publib.boulder.ibm.com/infocenter/rtc/v1r0m0/index.jsp

com.ibm.team.repository.ldap.findUsersByUserIdQuery=preferredIdentity\=?1
com.ibm.team.repository.ldap.baseGroupDN=ou\=memberlist,ou\=ibmgroups,o\=ibm.com
com.ibm.team.repository.ldap.findGroupsForUserQuery=uniquemember\={USER-DN}
com.ibm.team.repository.ldap.userAttributesMapping=userId\=preferredIdentity,name\=cn,emailAddress\=preferredIdentity
com.ibm.team.repository.ldap.membersOfGroup=uniquemember
com.ibm.team.repository.ldap.registryLocation=ldap\://XXXXXX\:389
com.ibm.team.repository.ldap.groupMapping=JazzAdmins\=XXXXXX,JazzUsers\=XXXXXX,JazzDWAdmins\=XXXXXX,JazzGuests\=XXXXXX
com.ibm.team.repository.ldap.baseUserDN=ou\=bluepages,o\=ibm.com

The database page of the setup wizard appears to be confused at the
start and if you switch it to db2 and enter the password and URL
(//localhost:50001/JAZZ:fullyMaterializeLobData=false;user=db2inst1;password={password};)
test connections works. However when you go to save you get this
message:

An error occurred while saving the configuration properties. Please
check your server log for more details.

Lots of database connection errors in the logs associated with this
activity.

Any suggestions would be much appreciated.