Dependency bundle not intalled - org.eclipse.emf.ecore
I just upgraded RQM v2.0.1 to QM v3.0.1
RQM server is on a VMWare server running Windows 2003. JTS server is running on a server running Windows 2008. We have upgraded RTC v2.0.2 to CCM 3.0.1 on a different VMWare and have run into no issues "provisioning" it and registering it with the new JTS server. Steps to upgrade RQM 2.0.1 to QM 3.0.1: 1. Upgraded RQM 2.0.1 to 2.0.1.1, iFix5 2. Installed QM 3.0.1 in a different location. 3. Ran the "Upgrade Script" to do the migration. All looks well, until I go to register the new QM on the JTS server admin page. I had an error regarding "Provisioning" on the RQM server. I looked on the RQM server and I saw this - in the Tomcat Widow that coms up after starting the CLM application: Sep 27, 2011 5:29:58 PM org.apache.catalina.core.AprLifecycleListener init INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\IBM\RQM301\server\jre\bin;.;C:\IBM\RCPR\dataconfig\jdk\jre\bin\classic;C:\IBM\RationalInsight\dataconfi g\jdk\jre\bin\classic;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\System Center Operations Manager 2007\;C:\WINDOWS\system32\WindowsPowerShell\v1.0 Sep 27, 2011 5:29:58 PM org.apache.coyote.http11.Http11BaseProtocol init INFO: Initializing Coyote HTTP/1.1 on http-9080 Sep 27, 2011 5:30:00 PM org.apache.coyote.http11.Http11BaseProtocol init INFO: Initializing Coyote HTTP/1.1 on http-9443 Sep 27, 2011 5:30:00 PM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 3391 ms Sep 27, 2011 5:30:01 PM org.apache.catalina.core.StandardService start INFO: Starting service Catalina Sep 27, 2011 5:30:01 PM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/5.5.30 Sep 27, 2011 5:30:01 PM org.apache.catalina.core.StandardHost start INFO: XML validation disabled Sep 27, 2011 5:30:20 PM org.apache.coyote.http11.Http11BaseProtocol start INFO: Starting Coyote HTTP/1.1 on http-9080 Sep 27, 2011 5:30:20 PM org.apache.coyote.http11.Http11BaseProtocol start INFO: Starting Coyote HTTP/1.1 on http-9443 Sep 27, 2011 5:30:20 PM org.apache.jk.common.ChannelSocket init INFO: JK: ajp13 listening on /0.0.0.0:9009 Sep 27, 2011 5:30:20 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=0/32 config=null Sep 27, 2011 5:30:20 PM org.apache.catalina.storeconfig.StoreLoader load INFO: Find registry server-registry.xml at classpath resource Sep 27, 2011 5:30:21 PM org.apache.catalina.startup.Catalina start INFO: Server startup in 20158 ms 2011-09-27 17:30:36,767 RQM ERROR eam.repository.provision.inter nal.ProvisionService - CRJAZ0281I The dependency bundle "org.eclipse.emf.ecore" is not installed. 2011-09-27 17:30:36,767 RQM ERROR com.ibm.team.repository.provision.internal.ProvisionService - CRJAZ0288I Failed to install the profile feature "com.ibm.team.jazz.foundation.server.jfs.feature" from the update site "file:jazz/sites/update-site" referenced in the profile file "C:\PROGRA~1\IBM\RQM301\server\conf\jazz\provision_profiles\profile.ini".com.ibm.team.repository.provision.ProvisionException: CRJAZ0281I The dependency bundle "org.eclipse.emf.ecore" is not installed. at com.ibm.team.repository.provision.internal.ProvisionService.installFeature(ProvisionService.java:365) at com.ibm.team.repository.provision.internal.ProvisionService.installFeature(ProvisionService.java:386) at com.ibm.team.repository.provision.internal.ProvisionService.installFeature(ProvisionService.java:386) at com.ibm.team.repository.provision.internal.ProvisionService.installFeature(ProvisionService.java:386) at com.ibm.team.repository.provision.internal.ProvisionService.installFeature(ProvisionService.java:466) at com.ibm.team.repository.provision.internal.ProvisionService.installFromProfiles(ProvisionService.java:764) at com.ibm.team.repository.provision.internal.ProvisionService.installFromProfile(ProvisionService.java:871) at com.ibm.team.repository.provision.internal.ProvisionService.installFromContextConfigurationUrl(ProvisionService.java:885) at com.ibm.team.repository.web.internal.Activator$1.run(Activator.java:123) at java.lang.Thread.run(Thread.java:811) 2011-09-27 17:30:36,782 RQM ERROR eam.repository.provision.internal.ProvisionService - CRJAZ0281I The dependency bundle "org.eclipse.emf.ecore" is not installed. 2011-09-27 17:30:36,782 RQM ERROR eam.repository.provision.internal.ProvisionService - CRJAZ0288I Failed to install the profile feature "com.ibm.team.rqm.prereqs.rtc.feature" from the update site "file:jazz/sites/rqm-prereqs-update-site" referenced in the profile file "C:\PROGRA~1\IBM\RQM301\server\conf\jazz\provision_profiles\rqm-prereqs-profile.ini". com.ibm.team.repository.provision.ProvisionException: CRJAZ0281I The dependency bundle "org.eclipse.emf.ecore" is not installed. at com.ibm.team.repository.provision.internal.ProvisionService.installFeature(ProvisionService.java:365) at com.ibm.team.repository.provision.internal.ProvisionService.installFeature(ProvisionService.java:466) at com.ibm.team.repository.provision.internal.ProvisionService.installFromProfiles(ProvisionService.java:764) at com.ibm.team.repository.provision.internal.ProvisionService.installFromProfile(ProvisionService.java:871) at com.ibm.team.repository.provision.internal.ProvisionService.installFromContextConfigurationUrl(ProvisionService.java:885) at com.ibm.team.repository.web.internal.Activator$1.run(Activator.java:123) at java.lang.Thread.run(Thread.java:811) 2011-09-27 17:30:37,001 RQM ERROR .ibm.team.jfs.app.discovery.utils.RootServicesUtil - While fetching the root services document from "https://192.168.2.248:9443/jazz/rootservices" a "404" HTTP status code was recieved 2011-09-27 17:30:37,470 RQM ERROR .ibm.team.jfs.app.discovery.utils.RootServicesUtil - While fetching the root services document from "https://192.168.2.248:9443/jazz/rootservices" a "404" HTTP status code was recieved 2011-09-27 17:30:37,517 RQM ERROR .ibm.team.jfs.app.discovery.utils.RootServicesUtil - While fetching the root services document from "https://192.168.2.24 8:9443/jazz/rootservices" a "404" HTTP status code was recieved 2011-09-27 17:30:37,611 RQM ERROR .ibm.team.jfs.app.discovery.util s.RootServicesUtil - While fetching the root services document from "https://192.168.2.248:9443/jazz/rootservices" a "404" HTTP status code was recieved 2011-09-27 17:30:37,657 RQM ERROR .ibm.team.jfs.app.discovery.utils.RootServicesUtil - While fetching the root services document from "https://192.168.2.248:9443/jazz/rootservices" a "404" HTTP status code was recieved === End of Tomcat Window output === ====== On the Admin web page of the RQM server this is seen on the "Provisioning" page: CRJAZ0300I Installing the feature "com.ibm.team.dashboard.common.jfs.feature_1.0.1.v20110524_1821". CRJAZ0300I Installing the feature "com.ibm.team.process.common.jfs.feature_1.1.1.v20110524_1821". CRJAZ0300I Installing the feature "com.ibm.team.foundation.common.jfs.feature_1.0.300.v20110524_1821". CRJAZ0300I Installing the feature "com.ibm.team.repository.common.jfs.feature_1.0.200.v20110524_1821". CRJAZ0288I Failed to install the profile feature "com.ibm.team.jazz.foundation.server.jfs.feature" from the update site "file:jazz/sites/update-site" referenced in the profile file "C:\PROGRA~1\IBM\RQM301\server\conf\jazz\provision_profiles\profile.ini". com.ibm.team.repository.provision.ProvisionException: CRJAZ0281I The dependency bundle "org.eclipse.emf.ecore" is not installed. at com.ibm.team.repository.provision.internal.ProvisionService.installFeature(ProvisionService.java:365) at com.ibm.team.repository.provision.internal.ProvisionService.installFeature(ProvisionService.java:386) at com.ibm.team.repository.provision.internal.ProvisionService.installFeature(ProvisionService.java:386) at com.ibm.team.repository.provision.internal.ProvisionService.installFeature(ProvisionService.java:386) at com.ibm.team.repository.provision.internal.ProvisionService.installFeature(ProvisionService.java:466) at com.ibm.team.repository.provision.internal.ProvisionService.installFromProfiles(ProvisionService.java:764) at com.ibm.team.repository.provision.internal.ProvisionService.installFromProfile(ProvisionService.java:871) at com.ibm.team.repository.provision.internal.ProvisionService.installFromContextConfigurationUrl(ProvisionService.java:885) at com.ibm.team.repository.web.internal.Activator$1.run(Activator.java:123) at java.lang.Thread.run(Thread.java:811) CRJAZ0303I The profile install from "file:jazz/sites/rqm-prereqs-update-site" was started at "Tue Sep 27 17:11:09 EDT 2011". CRJAZ0300I Installing the feature "com.ibm.team.rqm.prereqs.rtc.feature_3.0.1.v20110602_1036". CRJAZ0300I Installing the feature "com.ibm.team.interop.client.rest.rtc.feature_3.0.1.v20110602_1036". CRJAZ0299I Installing bundle from the URL "file:/C%3a/PROGRA~1/IBM/RQM301/server/conf/jazz/sites/rqm-prereqs-update-site/plugins/com.ibm.team.interop.client.rest_3.0.1.v20110602_1036.jar". === End of Provisioning Info === It appears that the RQM server is running, but it can't install some JAR file. I did not see this file in the installation folders. I saw a couple of other posts regarding this type of issue, but I did not see any resolution for them. Any help/advice is appreciated. |
8 answers
Ralph Schoon (63.5k●3●36●46)
| answered Sep 29 '11, 7:54 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Walter,
this is just a wide shot into the blue. I noticed you had installed into "Program Files". Dependent on the version of Windows this is a virtualized folder. Even if you are logged in as Administrator for instance in Windows 7 (potentially on Windows Server 2008) if you start tomcat from the shortcut it does not necessarily have enough rights to create files etc. What you can do is start a command line as administrator and start the server from there. In general I suggest do not install in those folders. I switch the Installation Manager folders as well as the shared and especially the install folders to some other dedicated path to avoid this issue. Not sure if this is the reason though. |
|
Hi Ralph,
Thanks for the quick reply. This RQM installation is being done on a Windows 2003 server (32 bit OS). I have used the info you have provided for the installation of the JTS v3.0.1 and RM v3.0.1 on the Windows 2008 server and that has worked well. This is all being done in our "Jazz Test environment". I have documenting all of the issues I have run into so that when we go to upgrade the "Production Jazz environment" we will know what to do if we see the same issues there. The document right now is 62 pages long. I am also "reusing" the existing RQM database as the database for the Datawarehouse. This is allowed (after deleting all the data from it). This is from Page 8 of the "Interactive upgrade guide for RQM. I have figured out how to resolve this issue. Before upgrading the RQM server, I upgraded our RTC server to CCM v3.0.1. This is the recommended method of upgrading to CLM - one application at a time. For that RTC/CCM upgrade, after installing CCM v3.0.1, I ran the "CCM Upgrade Script". Part of that script (Step 3 in particular) is the exact same step as what I ran on the RQM server from the "RQM Upgrade Script". This step has to be run on the new JTS server and I will explain why below. That may be the reason I was seeing errors about "identical" keys. To resolve this issue, I restored the database back to the state it was in the day before I ran the "CCM Upgrade Script". Then I ran Step 3 of the "RQM Upgrade Script" on the new JTS server, again. This time, the step completed without errors. I had to run Step 3 of the Upgrade Script on the new JTS server because the java version is different on it than the one on the RQM server. There is a Defect (#163859), about this situation here: https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=163859. This was encountered by someone at IBM and the reolution of the Defect was to write a "Tip" about this. I tried to see the "Tip", but I get "Access Denied" when I click on the link in the Defect. The situation that the author encountered is exactly the same as the one I encountered and here are the details from the Defect: JTS301+RM on Windows 64bit system RTC 2.x to CCM301 on Windows 32 bit RQM 2.x to QM301 on Windows 32 bit On upgrade #2 and upgrade #3 (RTC and RQM), I had to switch to the JTS system during one of the steps in the upgrade wrapper script sequence because of the following message: Step 3: Import user information into the JTS database ----------------------------------------------------- Directory: "z:\IBM\rrc3\server" Command: repotools-jts.bat -migration_importJTSData fromFile="C:\ibm\rqm3\server"\jts Data.tar createMappingFile="C:\ibm\rqm3\server"\appli-mapping.txt Enter to execute this step, to skip it or hit to cancel the script execution: E This version of z:\IBM\rrc3\server\jre\bin\java.exe is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher. The workaround is to run this step 3 from the JTS machine using a command like this, where x: refers back to the 32 bit system where the app like RTC or QM is installed: C:\IBM\rrc3\server>repotools-jts -migration_importJTSData fromFile=x:\ibm\rqm3\server\jtsData.tar createMappingFile=x:\ibm\rqm3\server\appli-mapping.txt then I went back to the 32 bit system and resumed ccm_upgrade or qm_upgrade and indicated I wanted to skip step 3.JTS301+RM on Windows 64bit system RTC 2.x to CCM301 on Windows 32 bit RQM 2.x to QM301 on Windows 32 bit On upgrade #2 and upgrade #3 (RTC and RQM), I had to switch to the JTS system during one of the steps in the upgrade wrapper script sequence because of the following message: Step 3: Import user information into the JTS database ----------------------------------------------------- Directory: "z:\IBM\rrc3\server" Command: repotools-jts.bat -migration_importJTSData fromFile="C:\ibm\rqm3\server"\jts Data.tar createMappingFile="C:\ibm\rqm3\server"\appli-mapping.txt Enter to execute this step, to skip it or hit to cancel the script execution: E This version of z:\IBM\rrc3\server\jre\bin\java.exe is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher. The workaround is to run this step 3 from the JTS machine using a command like this, where x: refers back to the 32 bit system where the app like RTC or QM is installed: C:\IBM\rrc3\server>repotools-jts -migration_importJTSData fromFile=x:\ibm\rqm3\server\jtsData.tar createMappingFile=x:\ibm\rq m3\server\appli-mapping.txt then I went back to the 32 bit system and resumed ccm_upgrade or qm_upgrade and indicated I wanted to skip step 3. === End of details from Defect === So, I have resolved this issue and I now have all of my CLM v3.0.1 applications up and running in our "Test" environment. Next up is the "Data Migration" on the upgraded RQM server. -Walter Hi Walter, |
|
Hi Ralph,
Thanks for the quick reply. This RQM installation is being done on a Windows 2003 server (32 bit OS). I have used the info you have provided for the installation of the JTS v3.0.1 and RM v3.0.1 on the Windows 2008 server and that has worked well. This is all being done in our "Jazz Test environment". I have documenting all of the issues I have run into so that when we go to upgrade the "Production Jazz environment" we will know what to do if we see the same issues there. The document right now is 62 pages long. I am also "reusing" the existing RQM database as the database for the Datawarehouse. This is allowed (after deleting all the data from it). This is from Page 8 of the "Interactive upgrade guide for RQM. I have figured out how to resolve this issue. Before upgrading the RQM server, I upgraded our RTC server to CCM v3.0.1. This is the recommended method of upgrading to CLM - one application at a time. For that RTC/CCM upgrade, after installing CCM v3.0.1, I ran the "CCM Upgrade Script". Part of that script (Step 3 in particular) is the exact same step as what I ran on the RQM server from the "RQM Upgrade Script". This step has to be run on the new JTS server and I will explain why below. That may be the reason I was seeing errors about "identical" keys. To resolve this issue, I restored the database back to the state it was in the day before I ran the "CCM Upgrade Script". Then I ran Step 3 of the "RQM Upgrade Script" on the new JTS server, again. This time, the step completed without errors. I had to run Step 3 of the Upgrade Script on the new JTS server because the java version is different on it than the one on the RQM server. There is a Defect (#163859), about this situation here: https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=163859. This was encountered by someone at IBM and the reolution of the Defect was to write a "Tip" about this. I tried to see the "Tip", but I get "Access Denied" when I click on the link in the Defect. The situation that the author encountered is exactly the same as the one I encountered and here are the details from the Defect: JTS301+RM on Windows 64bit system RTC 2.x to CCM301 on Windows 32 bit RQM 2.x to QM301 on Windows 32 bit On upgrade #2 and upgrade #3 (RTC and RQM), I had to switch to the JTS system during one of the steps in the upgrade wrapper script sequence because of the following message: Step 3: Import user information into the JTS database ----------------------------------------------------- Directory: "z:\IBM\rrc3\server" Command: repotools-jts.bat -migration_importJTSData fromFile="C:\ibm\rqm3\server"\jts Data.tar createMappingFile="C:\ibm\rqm3\server"\appli-mapping.txt Enter to execute this step, to skip it or hit to cancel the script execution: E This version of z:\IBM\rrc3\server\jre\bin\java.exe is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher. The workaround is to run this step 3 from the JTS machine using a command like this, where x: refers back to the 32 bit system where the app like RTC or QM is installed: C:\IBM\rrc3\server>repotools-jts -migration_importJTSData fromFile=x:\ibm\rqm3\server\jtsData.tar createMappingFile=x:\ibm\rqm3\server\appli-mapping.txt then I went back to the 32 bit system and resumed ccm_upgrade or qm_upgrade and indicated I wanted to skip step 3.JTS301+RM on Windows 64bit system RTC 2.x to CCM301 on Windows 32 bit RQM 2.x to QM301 on Windows 32 bit On upgrade #2 and upgrade #3 (RTC and RQM), I had to switch to the JTS system during one of the steps in the upgrade wrapper script sequence because of the following message: Step 3: Import user information into the JTS database ----------------------------------------------------- Directory: "z:\IBM\rrc3\server" Command: repotools-jts.bat -migration_importJTSData fromFile="C:\ibm\rqm3\server"\jts Data.tar createMappingFile="C:\ibm\rqm3\server"\appli-mapping.txt Enter to execute this step, to skip it or hit to cancel the script execution: E This version of z:\IBM\rrc3\server\jre\bin\java.exe is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher. The workaround is to run this step 3 from the JTS machine using a command like this, where x: refers back to the 32 bit system where the app like RTC or QM is installed: C:\IBM\rrc3\server>repotools-jts -migration_importJTSData fromFile=x:\ibm\rqm3\server\jtsData.tar createMappingFile=x:\ibm\rq m3\server\appli-mapping.txt then I went back to the 32 bit system and resumed ccm_upgrade or qm_upgrade and indicated I wanted to skip step 3. === End of details from Defect === So, I have resolved this issue and I now have all of my CLM v3.0.1 applications up and running in our "Test" environment. Next up is the "Data Migration" on the upgraded RQM server. -Walter Hi Walter, |
|
Ralph Schoon (63.5k●3●36●46)
| answered Sep 29 '11, 10:59 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Walter,
the information you are looking for is here: https://jazz.net/library/article/680 The link in the work item goes to the repository where we organize developing content for the Jazz.net site. From your description, if you have JTS and RM in one app server on one machine, you have to migrate RM first. Otherwise the general requirement is to install/go to JTS3.0.1 first. If you have installed RTC and JTS 3.0 this on one machine this typically means that you need to migrate RTC first. I am not sure which DB you mean when you say restore to the version before migrating. So, no sure if the next paragraph is relevant. If it was JTS: the scripts copy user data from the applications you upgrade in JTS and if you deleted that you might loose user information. You need the information from all tools there. The process does merging and there can be conflicts if you have users with same name but different ID's and such. |
|
Hi Ralph,
Thanks again for the quick reply. I was able to get to the "Tip" via your link. This next part is only if you have a "mixed" set of distributed servers. For example, two with a 32 bit OS on them and one with a 64 bit OS on it. I did use the "ignoreJTSVersionCheck" switch when I started the migration for CCM and RQM. The first step of the "Upgrade Script" has to be done manually. By the way, the article has a typo in several places. You can't use the minus sign in front of the switch. The command will return an error if you do that. It is "ignoreJTSVersionCheck" not "-ignoreJTSVersionCheck". That is on page 26 of my document. I don't think that we needed to "migrate" RM. For us, Requirements Manager is a new application. So, we have nothing to migrate it from. I do plan on migrating "internal requirements" that we had in RQM to RM. That will be done soon. The DB was for JTS. I think that in our case it worked out because all of the user data is the same for RQM and RTC. Right now, I am migrating "Reporting Data" and am running the "migrateDatawarehouse" script. I am pointing to a "xdc" file and after running the script I get the following message, but it doesn't say any thing about an error: !Missing bundle com.ibm.team.datawarehouse.service.rqm.internal.nls.messages! I am thinking that I may not have "reports" to migrate. I will open up a new topic on this. -Walter Hi Walter, |
|
Ralph Schoon (63.5k●3●36●46)
| answered Sep 29 '11, 12:06 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Walter,
please comment on the tip for the typos. With respect to the user data in JTS (even if RM is new you want your CCM and QM users merged) CCM and RQM had totally different internal UID's for the users. They try to merge the users to using one UID, as far as i know. I am not sure, even if you have visually the same users that you can assume that the users in the CCM arteficts match uid of the users imported into JTS from the RQM users. Not sure. I would just check. |
|
Hi Ralph,
I added the comment to the "Tip". I will run the Upgrade script on the RM application. Maybe "Upgrade" is the wrong name for it. Since QM, CCM, and JTS all seem to be communicating with each other, I think all is well with them. I am reluctant to have to go and run another upgrade script for any of the applications that appear to be working fine. Since this is "test" environment, I can easily check to make sure that the users' artifacts are the same across all applications. I am thinking that they should be since we are using LDAP and the "server.xml" file for the CCM and QM applications are the same as the one for the JTS server. I don't think that RM needs one since it is on the same server as JTS. I started another topic regarding the messages I am seeing when running the "migrateDatawarehouse" script on the upgraded QM server. Thanks for your help, -Walter Hi Walter, |
|
Ralph Schoon (63.5k●3●36●46)
| answered Sep 29 '11, 1:33 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Walter,
if RM is new you don't have to run the upgrade scripts. You just have to register and setup the application, I think. My concern was the migration and merge of the users of RM and CCM if that works as desired, all is well. If you missed it, we provide an upgrade workshop in the library that could be helpful. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.