After successful CLM install, can't log into CCM admin page
I installed JTS 3.0.1 as a fresh install on a new server (running 64bit OS - Windows 2008). A new Tomcat instance was installed on this server.
I installed the CCM application as an upgrade from RTC 2.0.0.2 on a different server with Windows 2003 (32 bit OS). I used "/jazz" as the root context for this installation. A new Tomcat instance was installed on this server.
I installed the QM application as an upgrade from RQM 2.0.1 on another, different server with Windows 2003 (32 bit OS). I used "/jazz" as the root context for this installation. A new Tomcat instance was installed on this server.
The registration of Quality Manager and CCM (RTC) went fine. I registered them using the "setup wizard" on the new JTS server.
I am able log into the "admin" Web UI of the upgraded QM server without any issues. However, I am having trouble logging into the new CCM application (the one I upgraded to from RTC 2.0.0.2). I can run the setup wizard for it, but I can't log into the "admin page" for it via the Web UI.
This is from the "jazz.log" file on the "CCM upgraded from RTC 2.0.0.2" server (user name is changed to a generic name here):
2011-09-13 13:46:16,419 WARN .team.repository.servlet.AbstractTeamServerServlet - CRJAZ1163I IllegalArgumentException processing GET request for com.ibm.team.repository.service.internal.ILicenseAdminRestService.getLicenseInfo(). CRJAZ1170I The request was made by user "<person>" from "10.1.10.160". CRJAZ1166I The stack trace hash is 5B9F1B085B62D7A638CD6F908B0271670953758E.
java.lang.IllegalArgumentException: An error response was received from the Jazz Team Server. Status=400. Message: The primary ContributorHandle for the ContributorHandle with the "" item ID could not be looked up.
I installed the CCM application as an upgrade from RTC 2.0.0.2 on a different server with Windows 2003 (32 bit OS). I used "/jazz" as the root context for this installation. A new Tomcat instance was installed on this server.
I installed the QM application as an upgrade from RQM 2.0.1 on another, different server with Windows 2003 (32 bit OS). I used "/jazz" as the root context for this installation. A new Tomcat instance was installed on this server.
The registration of Quality Manager and CCM (RTC) went fine. I registered them using the "setup wizard" on the new JTS server.
I am able log into the "admin" Web UI of the upgraded QM server without any issues. However, I am having trouble logging into the new CCM application (the one I upgraded to from RTC 2.0.0.2). I can run the setup wizard for it, but I can't log into the "admin page" for it via the Web UI.
This is from the "jazz.log" file on the "CCM upgraded from RTC 2.0.0.2" server (user name is changed to a generic name here):
2011-09-13 13:46:16,419 WARN .team.repository.servlet.AbstractTeamServerServlet - CRJAZ1163I IllegalArgumentException processing GET request for com.ibm.team.repository.service.internal.ILicenseAdminRestService.getLicenseInfo(). CRJAZ1170I The request was made by user "<person>" from "10.1.10.160". CRJAZ1166I The stack trace hash is 5B9F1B085B62D7A638CD6F908B0271670953758E.
java.lang.IllegalArgumentException: An error response was received from the Jazz Team Server. Status=400. Message: The primary ContributorHandle for the ContributorHandle with the "" item ID could not be looked up.
5 answers
I'll repeat the questions I asked in my response to your other post:
For RTC and RQM, when you upgrade from 2.X to 3.0.1, you need to export user information from the RTC and RQM databases, and import it into the JTS database, since the applications now use the JTS as a central user repository. Did you follow the upgrade instructions in http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.jazz.install.doc/topics/c_upgrade_clm_overview.html ?
For RTC and RQM, when you upgrade from 2.X to 3.0.1, you need to export user information from the RTC and RQM databases, and import it into the JTS database, since the applications now use the JTS as a central user repository. Did you follow the upgrade instructions in http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.jazz.install.doc/topics/c_upgrade_clm_overview.html ?
Hi John,
Yes, have followed the upgrade scripts detailed in the Interactive Upgrade guide (and in the Interactive Installation Guide). In fact, I have read over 20 documents related to upgrading/installing CLM 2011. I even went thru the CLM Workshop. I did get some useful info from the workshop. (The labs were mostly aimed at using WebSphere. We use Tomcat as our application server, so the info for WebSphere meant nothing to me. But I did get some info out of workshops). I have also been using the forums here for help when I encounter issues.
So, yes I DID export from both the RTC and RQM databases and imported the user information into the JTS database. I even had to do the "import" on the new JTS server that we are using (It is running a 64 bit OS and the RTC and RQM servers are each running a 32 bit OS. That was interesting to find out that I had to do that and that there was a "Tech Tip" for it).
Here is the proof. Sorry for the lengthy posting, but I want to assure you that I did do as the instructions said. I did this for both RTC and RQM:
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
This is from the "upgrade script" for migrating RTC v2.x to v3.0.1
Step 1 completed after adding the "ignoreJTSVersionCheck" switch.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Step 2: Export user information from the application database
------------------------------------------------------
Directory: "C:\Program Files\IBM\JazzTeamServer_1\server"
Command:
repotools-jazz.bat -migration_exportJTSData toFile=jtsData.tar
Enter to execute this step, to skip it or hit to cancel the script execution:
E
Repo Tools
Provisioning using "C:\Program Files\IBM\JazzTeamServer_1\server\conf\jazz\provision_profiles".
Change and Configuration Management - Core Libraries, Version 3.0.1 (RTC-I20110602-0252)
Jazz Foundation - Core Libraries, Version 3.0.1 (RJF-I20110602-0017)
CRJAZ1363I Loading the configuration from "file:conf/jazz/teamserver.properties".
CRJAZ1778I This server is configured as an application.
CRJAZ1970I The application is configured with:
Public URI: "https://SERVERNAME.net:9443/jazz"
Jazz Team Server location: "https://SERVERNAME.net:9443/jazz/"
CRJAZ1365I The server is attempting to connect to the following database: "//DBSERVER:1433;databaseName=rtc;user=xxxxxxxx;password=xxxxxxxx;"
CRJAZ1364I The connection to the following database was successful:
Db Product Name: Microsoft SQL Server
Db Product Version: 9.00.5057
Db URL: jdbc:sqlserver://DBSERVER:1433;databaseName=rtc;user=xxxxxxxx;password=xxxxxxxx;
Jdbc Driver Name: Microsoft SQL Server JDBC Driver 2.0
Jdbc Driver Version: 2.0.1803.100
CRJAZ8192I: Fulltext Index Location: C:\Program Files\IBM\JazzTeamServer_1\server\Program FilesIBMJazzTeamServer_1serverconfjazzindicesworkitemindexulltext_index\fulltext_index
CRJAZ8190I: The fulltext index should point to an absolute directory but is currently set to 'C:ProgramFilesIBMJazzTeamServer_1serverconfjazzindicesworkitemindexulltext_index'
The user "ADMIN" has logged in to the database "//DBSERVER:1433;databaseName=rtc;user=xxxxxxxx;password=xxxxxxxx;". Exporting the data from the database "//DBSERVER:1433;databaseName=rtc;user=xxxxxxxx;password=xxxxxxxx;" to the file "jtsData.tar".
Using encoding "windows-1252" for TAR file headers.
Exporting all the items present in the repository in offline mode.
Exporting com.ibm.team.repository/LicenseKey.
Exporting com.ibm.team.repository/LicenseType.
Exporting com.ibm.team.repository/ContributorRecord.
Exporting com.ibm.team.repository/ContributorDetails.
Exporting com.ibm.team.repository/LicenseAssignment.
Validating exported items...
Validating exported items for "com.ibm.team.repository"...
Exported 537 elements in 15860 ms.
com.ibm.team.repository
ContributorRecord : 226 items, 226 item states exported in 5610ms.
ContributorDetails : 223 items, 416 item states exported in 9234ms.
LicenseAssignment : 83 items, 83 item states exported in 704ms.
LicenseKey : 0 items, 0 item states exported in 16ms.
LicenseType : 5 items, 5 item states exported in 93ms.
Export completed successfully.
The user "ADMIN" has logged out of the database "//DBSERVER:1433;databaseName=rtc;user=xxxxxxxx;password=xxxxxxxx;".
Step 3: Import user information into the JTS database
-----------------------------------------------------
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
We skip this on the server with the 32 bit OS and run it on the server with the 64 bit OS.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Directory: "Z:\server"
Command:
repotools-jts.bat -migration_importJTSData fromFile="C:\Program Files\IBM\JazzTeamServer_1\server"\jtsData.tar createMappingFile="C:\Program Files\IBM\JazzTeamServer_1\server"\appli-mapping.txt
Enter to execute this step, to skip it or hit to cancel the script execution:
S
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Have to exit the script at Step 4 on the server with the 32 bit OS.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Step 4: Import JTS user information into the application database
-----------------------------------------------------------------
Directory: "C:\Program Files\IBM\JazzTeamServer_1\server"
Command:
repotools-jazz.bat -migration_importUserMapping fromMappingFile=appli-mapping.txt
Enter to execute this step, to skip it or hit to cancel the script execution:
I hit <Enter> to cancel the script execution at this point.
C:\Program Files\IBM\JazzTeamServer_1\server>upgrade\ccm_upgrade.bat
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
On the 64 bit server (JTS server), we ran the following:
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
C:\Program Files\IBM\JazzTeamServer\server>repotools-jts.bat -migration_importJTSData from
File="X:\RQM301\server"\jtsData.tar createMappingFile="X:\RQM301\server"\appli-mapping.txt
Repo Tools
Provisioning using "C:\Program Files\IBM\JazzTeamServer\server\conf\jts\provision_profiles".
Jazz Foundation - Core Libraries, Version 3.0.1 (RJF-I20110602-0017)
CRJAZ1363I Loading the configuration from "file:conf/jts/teamserver.properties".
CRJAZ1779I This server is configured as a JTS.
CRJAZ1971I The server is configured with:
Public URI: "https://tpaccpas172rtc.caremedic.net:9443/jts"
CRJAZ1365I The server is attempting to connect to the following database: "//DBSERVER:1433;databaseName=jts1;user=xxxxxxxx;password=xxxxxxxx;"
CRJAZ1364I The connection to the following database was successful:
Db Product Name: Microsoft SQL Server
Db Product Version: 9.00.5057
Db URL: jdbc:sqlserver://DBSERVER:1433;databaseName=jts1;user=xxxxxxxx;password=xxxxxxxx;
Jdbc Driver Name: Microsoft SQL Server JDBC Driver 2.0
Jdbc Driver Version: 2.0.1803.100
CRJAZ8192I: Fulltext Index Location: C:\Program Files\IBM\JazzTeamServer\server\conf\jts\indices\workitemindex\fulltext_index
CRJAZ8190I: The fulltext index should point to an absolute directory but is currently set
to 'conf/jts/indices/workitemindex'
The user "ADMIN" has logged in to the database "//DBSERVER:1433;databaseName=jts1;user=xxxxxxxx;password=xxxxxxxx;".
Importing the data from the file "X:\RQM301\server\jtsData.tar" into the database "//DBSERVER:1433;databaseName=jts1;user=xxxxxxxx;password=xxxxxxxx;".
Using encoding "windows-1252" for TAR file headers.
Reading the TAR file X:\RQM301\server\jtsData.tar...
Running pre import for "com.ibm.team.repository" component...
Running pre import for "com.ibm.team.process" component...
Running pre import for "com.ibm.team.dashboard" component...
Running pre import for "com.ibm.team.reports" component...
Running pre import for "com.ibm.team.links" component...
Running pre import for "com.ibm.team.jfs.resource" component...
Running pre import for "com.ibm.team.repository.friends" component...
Running pre import for "Full Text Migration Handler"...
Importing "LicenseType" items...
Importing "ContributorRecord" items...
Importing "ContributorDetails" items...
Importing "LicenseAssignment" items...
Rebuilding indices...
Running post import for "com.ibm.team.repository" component...
Running post import for "com.ibm.team.process" component...
Running post import for "com.ibm.team.dashboard" component...
Running post import for "com.ibm.team.reports" component...
Running post import for "com.ibm.team.links" component...
Running post import for "com.ibm.team.jfs.resource" component...
Running post import for "com.ibm.team.repository.friends" component...
Running post import for "Full Text Migration Handler"...
Post processing change events...
Verifying the repository contents using verification level 1.
Verifying items present in the "com.ibm.team.process" component.
Verifying items present in the "com.ibm.team.dashboard" component.
Verifying items present in the "com.ibm.team.repository" component.
Verifying context of com.ibm.team.repository/ChangeEvent items...
Verifying context of com.ibm.team.repository/LicenseType items...
Verifying context of com.ibm.team.repository/LicenseAssignment items...
Verifying context of com.ibm.team.repository/FloatingLicenseLease items...
Verifying context of com.ibm.team.repository/FloatingLicensePolicy items...
Verifying context of com.ibm.team.repository/ContributorDetails items...
Verifying context of com.ibm.team.repository/AuditableBaseline items...
Verifying context of com.ibm.team.repository/RepositoryRoot items...
Verifying context of com.ibm.team.repository/ServerVersionRecord items...
Verifying context of com.ibm.team.repository/ContributorRecord items...
Verifying context of com.ibm.team.repository/ContributorGroup items...
Verifying context of com.ibm.team.process/ProcessChangeEventCheck items...
Verifying context of com.ibm.team.process/ProjectArea items...
Verifying context of com.ibm.team.process/TeamArea items...
Verifying context of com.ibm.team.process/ProcessDefinition items...
Verifying context of com.ibm.team.process/ProcessDomainDefinition items...
Verifying context of com.ibm.team.process/DevelopmentLine items...
Verifying context of com.ibm.team.process/Iteration items...
Verifying context of com.ibm.team.process/IterationType items...
Verifying context of com.ibm.team.process/ProcessAttachment items...
Verifying context of com.ibm.team.process/ReadAccessList items...
Verifying context of com.ibm.team.process/ProjectLink items...
Verifying context of com.ibm.team.process/ProcessGenericItem items...
Verifying context of com.ibm.team.compatibilitypack/URIMapping items...
Verifying context of com.ibm.team.opaque/Opaque items...
Verifying context of com.ibm.team.diagnostictests/DiagnosticTestResultItem items...
Verifying context of com.ibm.team.repository.discovery/ServiceContributionResource items...
Verifying context of com.ibm.team.dashboard/Dashboard items...
Verifying context of com.ibm.team.dashboard/DashboardContributorInfo items...
Verifying context of com.ibm.team.applicationmigration/ApplicationMigrationStatus
items...
Verifying context of com.ibm.team.reports/ReportDescriptor items...
Verifying context of com.ibm.team.reports/FolderDescriptor items...
Verifying context of com.ibm.team.reports/ReportQueryDescriptor items...
Verifying context of com.ibm.team.links/AuditableLink items...
Verifying items present in the "com.ibm.team.reports" component.
Imported 13 items, 13 item states in 23869 ms. 247 item states skipped. Error importing 0 elements.
com.ibm.team.repository
ContributorRecord : 0 items, 0 item states imported.
ContributorDetails : 0 items, 0 item states imported.
LicenseAssignment : 11 items, 11 item states imported.
LicenseType : 2 items, 2 item states imported.
Migration completed successfully.
The user "ADMIN" has logged out of the database "//DBSERVER:1433;databaseName=jts1;
user=xxxxxxxx;password=xxxxxxxx;".
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
After exiting out of the script on the server with the 64 bit OS,
we now we run the remaining steps on the server with the 32 bit OS.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
C:\Program Files\IBM\JazzTeamServer_1\server>upgrade\ccm_upgrade.bat
=============================================
=== CCM Upgrade from 2.x to 3.0.1 ===
=============================================
Last execution was successfully stopped at step 3...
Do you want to restart the upgrade from current step 4 or a previous one?
Enter the step number you want to restart the upgrade from or to Cancel:
4
Step 4: Import JTS user information into the application database
-----------------------------------------------------------------
Directory: "C:\Program Files\IBM\JazzTeamServer_1\server"
Command:
repotools-jazz.bat -migration_importUserMapping fromMappingFile=appli-mapping.txt
Enter to execute this step, to skip it or hit to cancel the script execution:
E
Repo Tools
Provisioning using "C:\Program Files\IBM\JazzTeamServer_1\server\conf\jazz\provision_profiles".
Change and Configuration Management - Core Libraries, Version 3.0.1 (RTC-I20110602-0252)
Jazz Foundation - Core Libraries, Version 3.0.1 (RJF-I20110602-0017)
CRJAZ1363I Loading the configuration from "file:conf/jazz/teamserver.properties".
CRJAZ1778I This server is configured as an application.
CRJAZ1970I The application is configured with:
Public URI: "https://SERVERNAME.net:9443/jazz"
Jazz Team Server location: "https://SERVERNAME.net:9443/jazz/"
CRJAZ1365I The server is attempting to connect to the following database: "//DBSERVER:1433;databaseName=rtc;user=xxxxxxxx;password=xxxxxxxx;"
CRJAZ1364I The connection to the following database was successful:
Db Product Name: Microsoft SQL Server
Db Product Version: 9.00.5057
Db URL: jdbc:sqlserver://DBSERVER:1433;databaseName=rtc;user=xxxxxxxx;password=xxxxxxxx;
Jdbc Driver Name: Microsoft SQL Server JDBC Driver 2.0
Jdbc Driver Version: 2.0.1803.100
CRJAZ8192I: Fulltext Index Location: C:\Program Files\IBM\JazzTeamServer_1\server\Program
FilesIBMJazzTeamServer_1serverconfjazzindicesworkitemindexulltext_index\fulltext_index
CRJAZ8190I: The fulltext index should point to an absolute directory but is currently set
to 'C:Program FilesIBMJazzTeamServer_1serverconfjazzindicesworkitemindexulltext_index'
The user "ADMIN" has logged in to the database "//DBSERVER:1433;databaseName=rtc;user=xxxxxxxx;password=xxxxxxxx;".
Removing old user mapping data...
Removing contributor sync data...
Reading user mapping information...
Importing contributor record mapping information...
Application data imported successfully.
The user "ADMIN" has logged out of the database "//DBSERVER:1433;databaseName=rtc;user=xxxxxxxx;password=xxxxxxxx;".
=== End of steps to export and import data ===
I am now at the point of resolving some sort of "authorization" issue. I have been looking at these topics for assistance:
https://jazz.net/forums/viewtopic.php?t=17354&highlight=sufficient+privileges
https://jazz.net/forums/viewtopic.php?t=17417&highlight=sufficient+privileges
https://jazz.net/forums/viewtopic.php?t=17605&highlight=oauth+consumer
There more than the above ones, but suffice it to say, that I have been looking into and resolving issues as I encounter them.
Thanks for your help with the other questions that I have had. It is also good to know that i am not the only one running into these issues.
-Walter
Yes, have followed the upgrade scripts detailed in the Interactive Upgrade guide (and in the Interactive Installation Guide). In fact, I have read over 20 documents related to upgrading/installing CLM 2011. I even went thru the CLM Workshop. I did get some useful info from the workshop. (The labs were mostly aimed at using WebSphere. We use Tomcat as our application server, so the info for WebSphere meant nothing to me. But I did get some info out of workshops). I have also been using the forums here for help when I encounter issues.
So, yes I DID export from both the RTC and RQM databases and imported the user information into the JTS database. I even had to do the "import" on the new JTS server that we are using (It is running a 64 bit OS and the RTC and RQM servers are each running a 32 bit OS. That was interesting to find out that I had to do that and that there was a "Tech Tip" for it).
Here is the proof. Sorry for the lengthy posting, but I want to assure you that I did do as the instructions said. I did this for both RTC and RQM:
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
This is from the "upgrade script" for migrating RTC v2.x to v3.0.1
Step 1 completed after adding the "ignoreJTSVersionCheck" switch.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Step 2: Export user information from the application database
------------------------------------------------------
Directory: "C:\Program Files\IBM\JazzTeamServer_1\server"
Command:
repotools-jazz.bat -migration_exportJTSData toFile=jtsData.tar
Enter to execute this step, to skip it or hit to cancel the script execution:
E
Repo Tools
Provisioning using "C:\Program Files\IBM\JazzTeamServer_1\server\conf\jazz\provision_profiles".
Change and Configuration Management - Core Libraries, Version 3.0.1 (RTC-I20110602-0252)
Jazz Foundation - Core Libraries, Version 3.0.1 (RJF-I20110602-0017)
CRJAZ1363I Loading the configuration from "file:conf/jazz/teamserver.properties".
CRJAZ1778I This server is configured as an application.
CRJAZ1970I The application is configured with:
Public URI: "https://SERVERNAME.net:9443/jazz"
Jazz Team Server location: "https://SERVERNAME.net:9443/jazz/"
CRJAZ1365I The server is attempting to connect to the following database: "//DBSERVER:1433;databaseName=rtc;user=xxxxxxxx;password=xxxxxxxx;"
CRJAZ1364I The connection to the following database was successful:
Db Product Name: Microsoft SQL Server
Db Product Version: 9.00.5057
Db URL: jdbc:sqlserver://DBSERVER:1433;databaseName=rtc;user=xxxxxxxx;password=xxxxxxxx;
Jdbc Driver Name: Microsoft SQL Server JDBC Driver 2.0
Jdbc Driver Version: 2.0.1803.100
CRJAZ8192I: Fulltext Index Location: C:\Program Files\IBM\JazzTeamServer_1\server\Program FilesIBMJazzTeamServer_1serverconfjazzindicesworkitemindexulltext_index\fulltext_index
CRJAZ8190I: The fulltext index should point to an absolute directory but is currently set to 'C:ProgramFilesIBMJazzTeamServer_1serverconfjazzindicesworkitemindexulltext_index'
The user "ADMIN" has logged in to the database "//DBSERVER:1433;databaseName=rtc;user=xxxxxxxx;password=xxxxxxxx;". Exporting the data from the database "//DBSERVER:1433;databaseName=rtc;user=xxxxxxxx;password=xxxxxxxx;" to the file "jtsData.tar".
Using encoding "windows-1252" for TAR file headers.
Exporting all the items present in the repository in offline mode.
Exporting com.ibm.team.repository/LicenseKey.
Exporting com.ibm.team.repository/LicenseType.
Exporting com.ibm.team.repository/ContributorRecord.
Exporting com.ibm.team.repository/ContributorDetails.
Exporting com.ibm.team.repository/LicenseAssignment.
Validating exported items...
Validating exported items for "com.ibm.team.repository"...
Exported 537 elements in 15860 ms.
com.ibm.team.repository
ContributorRecord : 226 items, 226 item states exported in 5610ms.
ContributorDetails : 223 items, 416 item states exported in 9234ms.
LicenseAssignment : 83 items, 83 item states exported in 704ms.
LicenseKey : 0 items, 0 item states exported in 16ms.
LicenseType : 5 items, 5 item states exported in 93ms.
Export completed successfully.
The user "ADMIN" has logged out of the database "//DBSERVER:1433;databaseName=rtc;user=xxxxxxxx;password=xxxxxxxx;".
Step 3: Import user information into the JTS database
-----------------------------------------------------
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
We skip this on the server with the 32 bit OS and run it on the server with the 64 bit OS.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Directory: "Z:\server"
Command:
repotools-jts.bat -migration_importJTSData fromFile="C:\Program Files\IBM\JazzTeamServer_1\server"\jtsData.tar createMappingFile="C:\Program Files\IBM\JazzTeamServer_1\server"\appli-mapping.txt
Enter to execute this step, to skip it or hit to cancel the script execution:
S
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Have to exit the script at Step 4 on the server with the 32 bit OS.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Step 4: Import JTS user information into the application database
-----------------------------------------------------------------
Directory: "C:\Program Files\IBM\JazzTeamServer_1\server"
Command:
repotools-jazz.bat -migration_importUserMapping fromMappingFile=appli-mapping.txt
Enter to execute this step, to skip it or hit to cancel the script execution:
I hit <Enter> to cancel the script execution at this point.
C:\Program Files\IBM\JazzTeamServer_1\server>upgrade\ccm_upgrade.bat
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
On the 64 bit server (JTS server), we ran the following:
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
C:\Program Files\IBM\JazzTeamServer\server>repotools-jts.bat -migration_importJTSData from
File="X:\RQM301\server"\jtsData.tar createMappingFile="X:\RQM301\server"\appli-mapping.txt
Repo Tools
Provisioning using "C:\Program Files\IBM\JazzTeamServer\server\conf\jts\provision_profiles".
Jazz Foundation - Core Libraries, Version 3.0.1 (RJF-I20110602-0017)
CRJAZ1363I Loading the configuration from "file:conf/jts/teamserver.properties".
CRJAZ1779I This server is configured as a JTS.
CRJAZ1971I The server is configured with:
Public URI: "https://tpaccpas172rtc.caremedic.net:9443/jts"
CRJAZ1365I The server is attempting to connect to the following database: "//DBSERVER:1433;databaseName=jts1;user=xxxxxxxx;password=xxxxxxxx;"
CRJAZ1364I The connection to the following database was successful:
Db Product Name: Microsoft SQL Server
Db Product Version: 9.00.5057
Db URL: jdbc:sqlserver://DBSERVER:1433;databaseName=jts1;user=xxxxxxxx;password=xxxxxxxx;
Jdbc Driver Name: Microsoft SQL Server JDBC Driver 2.0
Jdbc Driver Version: 2.0.1803.100
CRJAZ8192I: Fulltext Index Location: C:\Program Files\IBM\JazzTeamServer\server\conf\jts\indices\workitemindex\fulltext_index
CRJAZ8190I: The fulltext index should point to an absolute directory but is currently set
to 'conf/jts/indices/workitemindex'
The user "ADMIN" has logged in to the database "//DBSERVER:1433;databaseName=jts1;user=xxxxxxxx;password=xxxxxxxx;".
Importing the data from the file "X:\RQM301\server\jtsData.tar" into the database "//DBSERVER:1433;databaseName=jts1;user=xxxxxxxx;password=xxxxxxxx;".
Using encoding "windows-1252" for TAR file headers.
Reading the TAR file X:\RQM301\server\jtsData.tar...
Running pre import for "com.ibm.team.repository" component...
Running pre import for "com.ibm.team.process" component...
Running pre import for "com.ibm.team.dashboard" component...
Running pre import for "com.ibm.team.reports" component...
Running pre import for "com.ibm.team.links" component...
Running pre import for "com.ibm.team.jfs.resource" component...
Running pre import for "com.ibm.team.repository.friends" component...
Running pre import for "Full Text Migration Handler"...
Importing "LicenseType" items...
Importing "ContributorRecord" items...
Importing "ContributorDetails" items...
Importing "LicenseAssignment" items...
Rebuilding indices...
Running post import for "com.ibm.team.repository" component...
Running post import for "com.ibm.team.process" component...
Running post import for "com.ibm.team.dashboard" component...
Running post import for "com.ibm.team.reports" component...
Running post import for "com.ibm.team.links" component...
Running post import for "com.ibm.team.jfs.resource" component...
Running post import for "com.ibm.team.repository.friends" component...
Running post import for "Full Text Migration Handler"...
Post processing change events...
Verifying the repository contents using verification level 1.
Verifying items present in the "com.ibm.team.process" component.
Verifying items present in the "com.ibm.team.dashboard" component.
Verifying items present in the "com.ibm.team.repository" component.
Verifying context of com.ibm.team.repository/ChangeEvent items...
Verifying context of com.ibm.team.repository/LicenseType items...
Verifying context of com.ibm.team.repository/LicenseAssignment items...
Verifying context of com.ibm.team.repository/FloatingLicenseLease items...
Verifying context of com.ibm.team.repository/FloatingLicensePolicy items...
Verifying context of com.ibm.team.repository/ContributorDetails items...
Verifying context of com.ibm.team.repository/AuditableBaseline items...
Verifying context of com.ibm.team.repository/RepositoryRoot items...
Verifying context of com.ibm.team.repository/ServerVersionRecord items...
Verifying context of com.ibm.team.repository/ContributorRecord items...
Verifying context of com.ibm.team.repository/ContributorGroup items...
Verifying context of com.ibm.team.process/ProcessChangeEventCheck items...
Verifying context of com.ibm.team.process/ProjectArea items...
Verifying context of com.ibm.team.process/TeamArea items...
Verifying context of com.ibm.team.process/ProcessDefinition items...
Verifying context of com.ibm.team.process/ProcessDomainDefinition items...
Verifying context of com.ibm.team.process/DevelopmentLine items...
Verifying context of com.ibm.team.process/Iteration items...
Verifying context of com.ibm.team.process/IterationType items...
Verifying context of com.ibm.team.process/ProcessAttachment items...
Verifying context of com.ibm.team.process/ReadAccessList items...
Verifying context of com.ibm.team.process/ProjectLink items...
Verifying context of com.ibm.team.process/ProcessGenericItem items...
Verifying context of com.ibm.team.compatibilitypack/URIMapping items...
Verifying context of com.ibm.team.opaque/Opaque items...
Verifying context of com.ibm.team.diagnostictests/DiagnosticTestResultItem items...
Verifying context of com.ibm.team.repository.discovery/ServiceContributionResource items...
Verifying context of com.ibm.team.dashboard/Dashboard items...
Verifying context of com.ibm.team.dashboard/DashboardContributorInfo items...
Verifying context of com.ibm.team.applicationmigration/ApplicationMigrationStatus
items...
Verifying context of com.ibm.team.reports/ReportDescriptor items...
Verifying context of com.ibm.team.reports/FolderDescriptor items...
Verifying context of com.ibm.team.reports/ReportQueryDescriptor items...
Verifying context of com.ibm.team.links/AuditableLink items...
Verifying items present in the "com.ibm.team.reports" component.
Imported 13 items, 13 item states in 23869 ms. 247 item states skipped. Error importing 0 elements.
com.ibm.team.repository
ContributorRecord : 0 items, 0 item states imported.
ContributorDetails : 0 items, 0 item states imported.
LicenseAssignment : 11 items, 11 item states imported.
LicenseType : 2 items, 2 item states imported.
Migration completed successfully.
The user "ADMIN" has logged out of the database "//DBSERVER:1433;databaseName=jts1;
user=xxxxxxxx;password=xxxxxxxx;".
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
After exiting out of the script on the server with the 64 bit OS,
we now we run the remaining steps on the server with the 32 bit OS.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
C:\Program Files\IBM\JazzTeamServer_1\server>upgrade\ccm_upgrade.bat
=============================================
=== CCM Upgrade from 2.x to 3.0.1 ===
=============================================
Last execution was successfully stopped at step 3...
Do you want to restart the upgrade from current step 4 or a previous one?
Enter the step number you want to restart the upgrade from or to Cancel:
4
Step 4: Import JTS user information into the application database
-----------------------------------------------------------------
Directory: "C:\Program Files\IBM\JazzTeamServer_1\server"
Command:
repotools-jazz.bat -migration_importUserMapping fromMappingFile=appli-mapping.txt
Enter to execute this step, to skip it or hit to cancel the script execution:
E
Repo Tools
Provisioning using "C:\Program Files\IBM\JazzTeamServer_1\server\conf\jazz\provision_profiles".
Change and Configuration Management - Core Libraries, Version 3.0.1 (RTC-I20110602-0252)
Jazz Foundation - Core Libraries, Version 3.0.1 (RJF-I20110602-0017)
CRJAZ1363I Loading the configuration from "file:conf/jazz/teamserver.properties".
CRJAZ1778I This server is configured as an application.
CRJAZ1970I The application is configured with:
Public URI: "https://SERVERNAME.net:9443/jazz"
Jazz Team Server location: "https://SERVERNAME.net:9443/jazz/"
CRJAZ1365I The server is attempting to connect to the following database: "//DBSERVER:1433;databaseName=rtc;user=xxxxxxxx;password=xxxxxxxx;"
CRJAZ1364I The connection to the following database was successful:
Db Product Name: Microsoft SQL Server
Db Product Version: 9.00.5057
Db URL: jdbc:sqlserver://DBSERVER:1433;databaseName=rtc;user=xxxxxxxx;password=xxxxxxxx;
Jdbc Driver Name: Microsoft SQL Server JDBC Driver 2.0
Jdbc Driver Version: 2.0.1803.100
CRJAZ8192I: Fulltext Index Location: C:\Program Files\IBM\JazzTeamServer_1\server\Program
FilesIBMJazzTeamServer_1serverconfjazzindicesworkitemindexulltext_index\fulltext_index
CRJAZ8190I: The fulltext index should point to an absolute directory but is currently set
to 'C:Program FilesIBMJazzTeamServer_1serverconfjazzindicesworkitemindexulltext_index'
The user "ADMIN" has logged in to the database "//DBSERVER:1433;databaseName=rtc;user=xxxxxxxx;password=xxxxxxxx;".
Removing old user mapping data...
Removing contributor sync data...
Reading user mapping information...
Importing contributor record mapping information...
Application data imported successfully.
The user "ADMIN" has logged out of the database "//DBSERVER:1433;databaseName=rtc;user=xxxxxxxx;password=xxxxxxxx;".
=== End of steps to export and import data ===
I am now at the point of resolving some sort of "authorization" issue. I have been looking at these topics for assistance:
https://jazz.net/forums/viewtopic.php?t=17354&highlight=sufficient+privileges
https://jazz.net/forums/viewtopic.php?t=17417&highlight=sufficient+privileges
https://jazz.net/forums/viewtopic.php?t=17605&highlight=oauth+consumer
There more than the above ones, but suffice it to say, that I have been looking into and resolving issues as I encounter them.
Thanks for your help with the other questions that I have had. It is also good to know that i am not the only one running into these issues.
-Walter
I'll repeat the questions I asked in my response to your other post:
For RTC and RQM, when you upgrade from 2.X to 3.0.1, you need to export user information from the RTC and RQM databases, and import it into the JTS database, since the applications now use the JTS as a central user repository. Did you follow the upgrade instructions in http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.jazz.install.doc/topics/c_upgrade_clm_overview.html ?
I'm not that familiar with the upgrade process, especially the scripts that can be used. But from what you posted, it looks to me like you exported user data from your RTC database, but then imported the user data that came from your RQM database into the JTS, creating a mapping file, and then imported the mapping information back into RTC. So it seems that the user mapping data you imported into RTC came from RQM. That may not be valid. If it isn't, I don't know how you would recover from that (other than doing the whole procedure all over again). It might be best if you ask for help from IBM support.
Hi John,
The lines for running the script on the 64 bit server do show the RQM database being used. But, that is just for showing an example. (I copied and pasted from the steps I used for the RQM upgrade instead of the RTC upgrade. They are both similar). Sorry for the confusion.
This is all being done in a test environment and I can start this all over again. I do have a lot of "notes and Tips/Tricks" to use the next time that go thru the upgrade process.
The only issue I am still working on is the "authorization" problems seen when using a user that is created by the upgrade process (i.e., jts_user). We use LDAP and that user (along with qm_user, ccm_user, and rm_user) is not in LDAP. So, that may be causing the issue. I saw a forum post where someone said that you could add those users to LDAP, but it was not necessary to do so.
Thanks for your help,
-Walter
The lines for running the script on the 64 bit server do show the RQM database being used. But, that is just for showing an example. (I copied and pasted from the steps I used for the RQM upgrade instead of the RTC upgrade. They are both similar). Sorry for the confusion.
This is all being done in a test environment and I can start this all over again. I do have a lot of "notes and Tips/Tricks" to use the next time that go thru the upgrade process.
The only issue I am still working on is the "authorization" problems seen when using a user that is created by the upgrade process (i.e., jts_user). We use LDAP and that user (along with qm_user, ccm_user, and rm_user) is not in LDAP. So, that may be causing the issue. I saw a forum post where someone said that you could add those users to LDAP, but it was not necessary to do so.
Thanks for your help,
-Walter
I'm not that familiar with the upgrade process, especially the scripts that can be used. But from what you posted, it looks to me like you exported user data from your RTC database, but then imported the user data that came from your RQM database into the JTS, creating a mapping file, and then imported the mapping information back into RTC. So it seems that the user mapping data you imported into RTC came from RQM. That may not be valid. If it isn't, I don't know how you would recover from that (other than doing the whole procedure all over again). It might be best if you ask for help from IBM support.
Forgot to mention that I can now get into the CCM Admin Web UI. The "authorization" issue is seen when I try to migrate Project Dashboards after logging into the Web Ui and accessing a project.
This is seen in the jazz.log on the CCM server:
ERROR service.internal.legacy.LegacyDashboardRestService - Dashboard migration encountered errors while migrating one or more dashboards. Please resolve the errors and re-run migration. See log for more details.
2011-09-15 09:13:13,738 WARN .team.repository.servlet.AbstractTeamServerServlet - CRJAZ1163I TeamRepositoryException processing GET request for com.ibm.team.repository.service.internal.ILicenseAdminRestService.getLicenseInfo(). CRJAZ1170I The request was made by user "wmansur" from "10.1.10.160". CRJAZ1167I The stack trace hash is 1B768C80A389CEE3466CACFA87D26AEB3B5F0F25, use it to locate the previously logged stack
== End of jazz.log snippet ===
This is seen from the Diagnostics page of the CCM server:
CRJAZ1992E The task "com.ibm.rqm.process.deployment.ProcessTemplatesMigrationTask" has failed with an unexpected error which has caused it to be unscheduled. The error message is "CRJAZ1832E The user configured to perform the request "SERVERNAME/jts/service/com.ibm.team.repository.service.internal.license.ILicenseRestService/assertLicense?operationId=com.ibm.team.process.server.saveProcessTemplate&user=https%3A%2F%2FSERVERNAME%3A9443%2Fjts%2FcontributorIdentity%2F_KGRY4CFWEdq-WY5y7lROQw&assign=true" on the JTS is not authorized. There may not be a functional user configured for the oauth consumer, or the functional user that is configured does not have sufficient privileges to perform the requested operation. Connection Error: Unauthorized". Please check your server logs for details. Once you have addressed the issues, you should restart the server to reschedule this background task.
=== End of Diagnostics message ===
I saw a post about this situation where you suggested that the author take a look on the Consumers page on the Admin Web UI of the JTS server and verify that the keys there matched the keys in the friendsconfig.rdf file for Requirements Manager (which was the application having the issue in that cast). In my case, those keys match. I did not see a friendsconfig.rdf file for JTS or CCM.
This is seen in the jazz.log on the CCM server:
ERROR service.internal.legacy.LegacyDashboardRestService - Dashboard migration encountered errors while migrating one or more dashboards. Please resolve the errors and re-run migration. See log for more details.
2011-09-15 09:13:13,738 WARN .team.repository.servlet.AbstractTeamServerServlet - CRJAZ1163I TeamRepositoryException processing GET request for com.ibm.team.repository.service.internal.ILicenseAdminRestService.getLicenseInfo(). CRJAZ1170I The request was made by user "wmansur" from "10.1.10.160". CRJAZ1167I The stack trace hash is 1B768C80A389CEE3466CACFA87D26AEB3B5F0F25, use it to locate the previously logged stack
== End of jazz.log snippet ===
This is seen from the Diagnostics page of the CCM server:
CRJAZ1992E The task "com.ibm.rqm.process.deployment.ProcessTemplatesMigrationTask" has failed with an unexpected error which has caused it to be unscheduled. The error message is "CRJAZ1832E The user configured to perform the request "SERVERNAME/jts/service/com.ibm.team.repository.service.internal.license.ILicenseRestService/assertLicense?operationId=com.ibm.team.process.server.saveProcessTemplate&user=https%3A%2F%2FSERVERNAME%3A9443%2Fjts%2FcontributorIdentity%2F_KGRY4CFWEdq-WY5y7lROQw&assign=true" on the JTS is not authorized. There may not be a functional user configured for the oauth consumer, or the functional user that is configured does not have sufficient privileges to perform the requested operation. Connection Error: Unauthorized". Please check your server logs for details. Once you have addressed the issues, you should restart the server to reschedule this background task.
=== End of Diagnostics message ===
I saw a post about this situation where you suggested that the author take a look on the Consumers page on the Admin Web UI of the JTS server and verify that the keys there matched the keys in the friendsconfig.rdf file for Requirements Manager (which was the application having the issue in that cast). In my case, those keys match. I did not see a friendsconfig.rdf file for JTS or CCM.
Hi John,
The lines for running the script on the 64 bit server do show the RQM database being used. But, that is just for showing an example. (I copied and pasted from the steps I used for the RQM upgrade instead of the RTC upgrade. They are both similar). Sorry for the confusion.
This is all being done in a test environment and I can start this all over again. I do have a lot of "notes and Tips/Tricks" to use the next time that go thru the upgrade process.
The only issue I am still working on is the "authorization" problems seen when using a user that is created by the upgrade process (i.e., jts_user). We use LDAP and that user (along with qm_user, ccm_user, and rm_user) is not in LDAP. So, that may be causing the issue. I saw a forum post where someone said that you could add those users to LDAP, but it was not necessary to do so.
Thanks for your help,
-Walter
I'm not that familiar with the upgrade process, especially the scripts that can be used. But from what you posted, it looks to me like you exported user data from your RTC database, but then imported the user data that came from your RQM database into the JTS, creating a mapping file, and then imported the mapping information back into RTC. So it seems that the user mapping data you imported into RTC came from RQM. That may not be valid. If it isn't, I don't know how you would recover from that (other than doing the whole procedure all over again). It might be best if you ask for help from IBM support.