I'm unable to download the featured based launch jar file. It looks like the file is in the wrong format.

Link: https://jazz.net/wiki/pub/Main/FeatureBasedLaunches/com.ibm.team.dev.launch_0.3.3.201004231417.jar

I can't get to the wiki at all, right now. i use a download manager and the file ended up on my disk named com.ibm.team.dev.launch_0.3.3.201004231417.jar.txt I just removed the .txt ending and all was working. On windows this is sometimes hard to detect if you don't switch to show all file extensions.

I was able to download the file after removing the .txt ext. Thanks!

Hi,

I got an error when I tried to load Repository Workspace in RTC 4.0. See error below. Do you know where I went wrong during the installation? Thanks!

My steps:
1. Right click on RTC Extension Workspace under "My Repository Workspace"
2.Click on Load
3. Select "Find and Load Eclipse Projects"
4. Click Next

Unable to obtain license to read SCM related data: CRJAZ1832E The user configured to perform the request "https://localhost:9443/jts/service/com.ibm.team.repository.service.internal.license.ILicenseRestService/assertLicense?operationId=com.ibm.team.scm.readaccess.general&user=https%3A%2F%2Flocalhost%3A9443%2Fjts%2FcontributorIdentity%2F_KGRY4CFWEdq-WY5y7lROQw&assign=false" 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.
Unable to obtain license to read SCM related data: CRJAZ1832E The user configured to perform the request "https://localhost:9443/jts/service/com.ibm.team.repository.service.internal.license.ILicenseRestService/assertLicense?operationId=com.ibm.team.scm.readaccess.general&user=https%3A%2F%2Flocalhost%3A9443%2Fjts%2FcontributorIdentity%2F_KGRY4CFWEdq-WY5y7lROQw&assign=false" 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.

I'm also getting the following error on the Active Users page in CCM - ccm/admin#action=com.ibm.team.repository.manageUsers

The user configured to perform the request "https://localhost:9443/jts/service/com.ibm.team.repository.service.internal.IExternalUserRegistryRestService/isExternalRegistryWriteable" 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

I would suggest to ask a question in the forum, to track this. I would check the licenses assigned to the user. You need a 10 free developers that you uploaded.

Just finished the workshop. One of the best I had.
It is a must for each RTC implementer.

I'm having trouble importing the workshop repositories. It appears to be a data versioning issue. I installed the server using the RTC 4.0.0.1 web installer. When I run the importer to bring in the repository data currently linked above (RTCExtensionsJTSRepository-40-20120703.tar), I get the following error:

Specifics: CRJAZ2403E
The version of the data that you are trying to import does not match
the version of this tool. The "com.ibm.team.repository" component in
the exported file uses version "28". However, this import tool can
handle only version "30".

Advice on how to proceed? Was it a mistake to follow the advice to grab the latest-and-greatest, i.e. is this more likely to work if I use the 4.0 web installer instead? Any other approach that doesn't throw away the bringup work I've done so far?

Thanks.

Hi, the article lists build basis 4.0. I assume you can set up on 4.0 and then upgrade to 4.0.0.1 which was not out when the update to the workshop was done. In the past repotools sometimes could import from older versions. It appears this is no longer true.

I am not sure if you should rather post a question on the forum then comment here. It gets a bit too much here I guess 8-)

After importing the 10 developer free licenses, I get the following message :
This Client Access License is disabled: The license key "Rational Team Concert-10 Free" is not compatible with the license type "Developer". It is possible that the key was migrated from an earlier version and is now incompatible with the current version. To fix the problem you may want to either replace the key with an updated version or remove the key if it is possible.
As a consequence, ADMIN cannot get developer license and I cannot start the workshop..
Any Idea ??

As an alternative scenario, is it possible to start from a standard installation and create/import the necessary data ?

Please be aware that you HAVE to use the RTC version that is the build basis. It has to be 4.0, not 4.0.0.1 and not 4.0.1. Make sure you download the keys from that version. At this point the code is in the workshop repository you build up. It is not published alone and actually there are several baselines you load. You have to go through a successful setup to get it. Once you have it, you can import it somewhere else.

However, if you use a different version of RTC you might not be able to get the SDK set up, because the license files might be called differently.

I just tried to upload the 10 Free 4.0 licenses https://jazz.net/downloads/rational-team-concert/releases/4.0/RTC-Developer-10-C-License-4.0.zip up into my 4.0 install of the workshop based on https://jazz.net/downloads/rational-team-concert/releases/4.0?p=allDownloads and the licenses work ok.

Hello!
I want to know when can I get these three tar files with RTC 4.0.1 version? Because our server is RTC 4.0.1 and also the sdk I have got is RTC SDK 4.0.1, I think develop in 4.0.1 is better, isn't it?

I have no plan on updating the workshop. I can't possibly keep up with the release anyway.

My suggestion would be: Set up the workshop with 4.0 and run it there. Then you can either upgrade the server with the workshop material to your version, or you set up a separate dev environment for the newest version, following lab 1, skipping the repotools import.

Separate dev environment is inconvenient, I will try install 4.0 RTC and upgrade it after import these tar files. However, thanks.

In the PDF, in the Introduction, it states that "these instructions are written specifically for RTC 3.0.1 on Windows®. ". In the "Setting Up" section, it has the correct 4.0 statement. I believe the Introduction needs updated.
Also, the Introduction lists the other TAR files with the -301- name instead of the -40- name, which needs updated (The Setting Up" section also has the correct -40- names.

Section 1.1, the text in the URL says releases/4.0? but if you look at the actual URL, it goes to 3.0.1

Thanks Susan, I will fix that. The workshop is for 4.0 and I tried hard to find all references to 3.x. Not sure why I missed those.

Hi Susan, thanks so much for the hints. I have fixed the issues you found, the changes will go online in the next few days.

Hi,
I tried to setup the workshop with RTC4.0. Setup completed okay. The repotool commands also executed successfully. Now when I try to load the RTC Extention Workspace by right click on workspace->Load->Find and Load Eclipse projects, I got the following error and not able to proceed further

"Unable to obtain license to read SCM related data: An error response was received from the Jazz Team Server. Status=400. Message: CRJAZ0972I The "com.ibm.team.scm.readaccess.general" operation was forbidden because the "Developer" license is currently deactivated.."

Please create a question in the forum. You can put a link to the question here or send me a message (e-mail address in the article). It does not scale discussing things here. My best guess is you forgot to upload the 10 Free developer license.

Hi Ralph,

I have some errors at step 1.2 and posted a question in the forum. Could you please take a look?

https://jazz.net/forum/questions/99728/rtc-40-extension-workshop-2-errors-after-step-12

Thanks for this great workshop!
I have a problem during the setup of the RTC environment. I followed the steps but get some problems, there are some exceptions in RTC which cause some pages not to work. The most disturbing problem I have: When I try to follow your Step 1.6 (Test the jetty based server launch), step 29 (connect with the browser), the startup page with the login will not show, only the word "Loading..."
In the RTC Client I get the exception "2013-03-18 16:02:34.447:WARN::/jazz/web/_style/
java.lang.NullPointerException at net.jazz.ajax.model.Sprite.writeCSS(Sprite.java:125)"

This seems to relate to the error I got with Tomcat "org.eclipse.core.runtime.AssertionFailedException: assertion failed: Sprite generation is non-deterministic
org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)
net.jazz.ajax.model.SpriteLayout$Algorithm$1.compare(SpriteLayout.java:130)"
(which was also mentioned in https://jazz.net/forum/questions/87244/rtc-40-install-error-assertionfailedexception-sprite-generation-is-non-deterministic - with no solution given).
I tried to debug this situation and notice that the final List<URL> images has some entries which are not valid (some of the contained "images" are empty.
My knowledge of RTC is not sufficient to find the exact reason for this.
My computer is a Windows 2008 server - I had RTC installed on it before, so the problem might stem from some previous, not completely cleaned up environment.
a) can you help me in finding the core reason for this problem?
b) if not, can you tell me what I have to remove from my computer to be able to begin again with the installation from scratch with no traces of an old installation that might disturb me?
Thanks very much and best regards,
Mike

oops - I just saw your advice to post such questions in the forum - sorry, will do this now...

I'm trying to set this up on a back-up Windows 7 64-bit machine. I've gone through down to the first "start the server". I used all defaults with the exception of changing the various paths as stated in the pdf instructions.

When I run the server.startup.bat, it runs through the bat file but then when it *should* open a new window and start Tomcat, I think something blinks but I never get Tomcat started. There are also no logs generated under server\tomcat\logs.

Any idea how to debug this or what may be wrong? I've also tried using the Windows start menu items but I get the same nothing-ness.
Susan

This should really be a forum question.

Two pitfalls, Installing in Program Files - the server should start but very quickly and then nothing works.
If it just blinks it is typically a Java Error very early in the launch of tomcat. Follow https://jazz.net/forum/questions/82298/jts-is-not-starting-on-tomcat-40 and in the batch replace start by run to debug what's going on.

Moving to 2G worked (question 82298). Perhaps you could update the workshop to have a pointer to this.

For people struggling with the "expired license" problem: RTC was telling me that the Developer license was expired, even after uploading the 10 free developer licenses. I couldn't fix it through the web UI. The only way I could fix the problem was through the Eclipse client, by right-clicking the "ADMIN@localhost" repository connection, selecting "Administer > Open Users...", choosing the ADMIN user, and assigning the Developer license there. After that I could load the workshop sources without the license error.

I don't understand why and how to use "the Jetty Based Server"?
It is useless, but makes the simple thing complex.
I think using Tomcat server to develop and test extensions is enough.

If you like to redeploy on Tomcat for any minor change to your plugin for debugging, go ahead. In the meantime I will save time using the jetty based launches until I am pretty sure the extensions work as expected, before going to deploy it on a Tomcat.

Hi, Ralph Schoon, could you update this article for RTC 4.0.4(not only the text, but also the picture/source code, etc)?
I have encountered the problem:
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=292476

Albert, I ran the workshop with 4.0.4 (and 4.0.5 RC1) and it still works, even if the SDK code might be changed a bit, like in the screen shot, you should be able to run it. I will certainly not be able to update the workshop for each release and have not planned to do so. If the SDK code slightly changes, the pictures might be a little bit different.

I have created something that can remove the requirement to install into 4.0 and upgrade, but It is still under legal review if we can publish it.

What I could do maybe for an upcoming major release is to remove screen shots for code that is in the SDK and might change in the future. Maybe blur the code that is unimportant. At least if it is unimportant for running the workshop in terms of it still works if changed slightly.

Hi, Ralph Schoon, could you help this: https://jazz.net/forum/questions/137132/which-feature-is-corresponding-to-the-plug-in-comibmteamfilesystemcommonworkitems

Hi Ralph. I got an error when I tried to load Repository Workspace in RTC 4.0.
Could you help me? Thanks!
https://jazz.net/forum/questions/143009/rational-team-concert-40-extensions-workshop-error

Just to let you know:

The workshop packaging and workbook was updated to address various issues that users experienced during setup. For example the new version is now compatible and can be used with all 4.x Versions of RTC. The temporary licenses of the RTC server will not be expired and the setup process is less manual. To address this, the new version of the workshop provides a tool that uses the Plain Java Client Libraries to populate the RTC server with the development data. This change allows to run the workshop against any 4.0.x version of RTC. It has been tested with several versions up to 4.0.6. This also makes the code for the extension developed in the workshop available as archive files without having to set up the workshop RTC instance.

I think this should address numerous issues we have seen here and in the forum.

Hello Ralph

When i run the Rational Team Concert launchpad , launchpad.exe i get the following error
The com.ibm.team.install.jfs.app.jts package specified in the C:\RTC40Dev\Installs\JazzTeamServer\im\win32.win32.x86\install-server.xml file cannot be found.
The com.ibm.team.install.jfs.app.product-clm package specified in the C:\RTC40Dev\Installs\JazzTeamServer\im\win32.win32.x86\install-server.xml file cannot be found.
The com.ibm.team.install.jfs.app.rtc package specified in the C:\RTC40Dev\Installs\JazzTeamServer\im\win32.win32.x86\install-server.xml file cannot be found.
The com.ibm.team.install.jfs.app.rdm package specified in the C:\RTC40Dev\Installs\JazzTeamServer\im\win32.win32.x86\install-server.xml file cannot be found.
The com.ibm.team.install.jfs.app.rqm package specified in the C:\RTC40Dev\Installs\JazzTeamServer\im\win32.win32.x86\install-server.xml file cannot be found.

Please suggest.

Launchpad is the installation manager. I can only assume that you did not follow the instructions close enough. If you use the Web Install, you should not see this. I don't know what happens, since you don't even mention the step.

If you use a installation manager repository, the repository is broken.

The launch confuguration states the path for the following two files
[...]RTC Extension Workshop Configuration/conf/jazz/scr.xml
[...]RTC Extension Workshop Configuration/conf/jazz/services.xml

which are not present in the downloadable zip file.
This leads to FileNotFound exceptions when running the jetty launches.

I should have read page 30 Step 19.
Sorry

I should have read page 30 Step 19.
Sorry

Thanks Kevin!

For information about the workshop and the 5.0 version see: https://rsjazz.wordpress.com/2014/06/11/running-rtc-4-x-extensions-workshop-with-rtc-5-0/

There is an error shown in some of the views, but it seems not to be an issue,

I am developing extensions for RTC EE but when I set the Jetty server everything works fine except on Jetty in Project Area > Process Configuration > Team Configuration > Operation Behaviour does not show "Promote" (table)
On Tomcat exists this option but on Jetty it does not exists.
In addition in both project areas (Tomcat & Jetty) in the perspective Work Items > Enterprise Extensions the folder is shown.
Any idea?

As far as I am aware the SDK does not ship the content for the enterprise extensions. You won#t see them in Jetty.

I have not done extending for them. I would suggest to ask on the forums what other users have experienced and how to proceed.

@Fran Burgos
I found the following answers useful in setting up a debug configuration for RTC EE:
https://jazz.net/forum/questions/100624/why-cant-i-create-a-build-using-the-jetty-rtc-server
https://jazz.net/forum/questions/102155/why-cant-i-access-my-team-repository-while-testing-and-debugging-an-rtc-extension

@Nicolas Bros thank you so much. The links were very useful. I have been able to create an enterprise extension.

On the other hand I noticed with RTC 4.0.7 Run Configurations > JUnit2 Launch > [RTCExt] Create RTC Test Database does not show. But in RTC 4.0.5 is shown correctly. (I have tested in two different Virtual Machines and this always happens. It is curious)

I am doing the workshop on Mac OS (yes, I know it's unsupported, but it is used quite a bit in development). When I launch the Jetty server for debug (page 52 - [RTCExt] Jetty RTC Server), no output appears in the Console view and, no surprise, I can't connect to Jetty on port 7443. I've let it run for about 15 minutes. Any thoughts?

Additional detail to add to the comment above: I'm running CLM 5.0.2 (I did read that the workshop works on 5.x)

@Daniel Chirillo, did you ever resolve this? I'm seeing the same thing.

@Steve Dearth - No I did not. I did the workshop on a Windows VM.

@Steve Dearth - No I did not. I did the workshop on a Windows VM.

@Steve Dearth - No I did not. I did the workshop on a Windows VM.

I'm currently exercising this extension workshop to set development environment to extend RTC

Instead of using web installers to install Server and client I used Installation managers to install Jazz team server and RTC eclipse client. However directory in my system is same as the one shown in workshop. When I open WorkshopSetup.bat in notepad first line I see is

"set JAVA_HOME=..\TeamConcert\jazz\client\eclipse\jdk" but in my system jdk folder is directly under TeamConcert folder therefore in WorkshopSetup.bat file I changed first line as "set JAVA_HOME=..\TeamConcert\jdk"
When I try to run WorkshopSetup.bat file it is showing me error as "Could not find or load main class WorkshopSetup.jar" How do I resolve this problem I am performing this workshop on CLM version 5.0.2

See my answer in the forum. I don't believe this is related to the JAVA_HOME path, as Java starts.

Can you please provide the link of forum where you have given the answer

You can't remember your own question in the forums? https://jazz.net/forum/questions/208865/could-not-find-or-load-main-class-workshopsetupjar

We have customers inquiring about how to setup WLP against the earlier jetty setups, while the earlier setup documentation (https://jazz.net/wiki/bin/view/Main/AppSdk) suggests that the configuration is not covered under standard support, could you please point the readers of this article to the technote that refers to the WLP configuration steps for the same.

We have customers inquiring about how to setup WLP against the earlier jetty setups, while the earlier setup documentation (https://jazz.net/wiki/bin/view/Main/AppSdk) suggests that the configuration is not covered under standard support, could you please point the readers of this article to the technote that refers to the WLP configuration steps for the same.

What exactly is WLP?

WebSphere Liberty Profile, I suppose

There is almost no difference to how this runs with Tomcat or WAS Libery Profile.

Some hints here: https://rsjazz.wordpress.com/2016/02/04/running-the-rtc-extensions-workshop-with-rtc-6-0-x/

And that does not have anything to do with Jetty. The workshop still will use Jetty for debugging the extensions.

Hi Ralph,
I am using CLM 6.0.3 RTC extension workshop. When trying to setup the Jetty based debug server lunch could not find the Eclipse->Run Configurations -> JUnit2 Launch > [RTCExt]. Is there any work around to fix this problem. The workshop setup tool ran successfully before setting up these steps.

If you have that symptom, you missed a step in the workshop e.g. loading the repository workspace - because that contains the run configuration or you failed to deploy the feature based launches.

Hello, Ralf.
Just one question related to the BuildOnStateChangeAspectEditor.getWorkItemTypes and BuildOnStateChangeAspectEditor.getBuildDefinitions
A new thread is spawned using the method "PlatformUI.getWorkbench().getActiveWorkbenchWindow().run" with the first parameter (fork) equal to true.
However according to the documentation the "run" method blocks until the runnable has been run, regardless of the value of fork. As the caller is the UI thread it will be blocked until the "runnable" is run.
In the "BuildOnStateChangeAspectEditor" code itself there is a comment: "This could hit the server so move off UI thread."

What is the added value of executing the code in another thread if the UI thread is also blocked until the second thread has complemented its work?

Hi Krasimir,

I have really not looked into that detail. I would suggest to check the code in other advisors/follow up actions and how they do it today.
One point to make here, the aspect editor runs in the Eclipse UI, so I don't see what the problem would be. There is no server side configuration I am aware of.

About:

Lab 2 – Create a Simple Participant
__38. Understanding the service plug-in Eclipse project.
__g. Unfortunately, this is not the case for the children of the (prerequisites) node. You can
edit the nodes that are there, but to add a new (requiredService) node, you need to edit
the xml on the plugin.xml tab.

You don't need to edit the xml on the plugin.xml tab anymore if you copy the file 'prerequisites.exsd' from RTC SDK to the folder 'plugins\com.ibm.team.repository.service_1.3.200.v20141015_2351\schema'. (Why this file is still missing from the default RTC installation is a mistery...)
Cheers.

Hi, Ralph. I'm wondering if you can give some hint of my problem. basically I can not proceed now.

I'm doing this workshop using RTC 6.0.5, currently stuck in section 1.6, step 35.c. As soon as I click "JUnit Launch > [RTCExt] Create RTC Test
Database", I've got :

An error has occurred. See error log for more details.
java.lang.NullPointerException

Four errors appears in error log view.

1) Conflicting handlers for org.eclipse.ui.edit.copy: {ActionHandler(com.ibm.team.dev.launch.ui.LaunchToolbar$CopyAction@744da252)} vs {org.eclipse.ui.internal.handlers.WidgetMethodHandler@2779bd7c}

2) Conflicting handlers for org.eclipse.ui.edit.paste: {org.eclipse.ui.internal.handlers.WidgetMethodHandler@18a4b2b} vs {ActionHandler(com.ibm.team.dev.launch.ui.LaunchToolbar$PasteAction@4159587c)}

3) Problems occurred when invoking code from plug-in: "org.eclipse.jface".
Exception Stack trace :
java.lang.NullPointerException
at org.eclipse.pde.internal.core.MinimalState.addBundle(MinimalState.java:129)
at org.eclipse.pde.internal.core.PDEState.createNewTargetState(PDEState.java:160)
at org.eclipse.pde.internal.core.PDEState.readTargetState(PDEState.java:129)
at org.eclipse.pde.internal.core.PDEState.(PDEState.java:101)
at org.eclipse.pde.internal.core.PluginModelManager.initializeTable(PluginModelManager.java:515)
at org.eclipse.pde.internal.core.PluginModelManager.getWorkspaceModels(PluginModelManager.java:1037)
at org.eclipse.pde.core.plugin.PluginRegistry.getWorkspaceModels(PluginRegistry.java:209)
at org.eclipse.pde.internal.core.PDEExtensionRegistry.getModels(PDEExtensionRegistry.java:59)
at org.eclipse.pde.internal.core.PDERegistryStrategy.getContributionsTimestamp(PDERegistryStrategy.java:301)
at org.eclipse.core.internal.registry.ExtensionRegistry.(ExtensionRegistry.java:682)
at org.eclipse.core.runtime.RegistryFactory.createRegistry(RegistryFactory.java:58)
at org.eclipse.pde.internal.core.PDEExtensionRegistry.createRegistry(PDEExtensionRegistry.java:85)
at org.eclipse.pde.internal.core.PDEExtensionRegistry.getRegistry(PDEExtensionRegistry.java:77)
at org.eclipse.pde.internal.core.PDEExtensionRegistry.getExtensionPoint(PDEExtensionRegistry.java:134)
at org.eclipse.pde.internal.core.PDEExtensionRegistry.findExtensions(PDEExtensionRegistry.java:205)
at org.eclipse.pde.internal.core.TargetPlatformHelper.getProductNameSet(TargetPlatformHelper.java:232)
at org.eclipse.pde.internal.core.TargetPlatformHelper.getProductNames(TargetPlatformHelper.java:247)
at org.eclipse.pde.core.plugin.TargetPlatform.getProducts(TargetPlatform.java:147)
at org.eclipse.pde.internal.ui.launcher.ProgramBlock.createProductSection(ProgramBlock.java:105)
at org.eclipse.pde.internal.ui.launcher.ProgramBlock.createControl(ProgramBlock.java:96)
at org.eclipse.pde.ui.launcher.MainTab.createControl(MainTab.java:79)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.showInstanceTabsFor(LaunchConfigurationTabGroupViewer.java:817)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.displayInstanceTabs(LaunchConfigurationTabGroupViewer.java:748)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$8.run(LaunchConfigurationTabGroupViewer.java:635)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.inputChanged(LaunchConfigurationTabGroupViewer.java:652)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput0(LaunchConfigurationTabGroupViewer.java:613)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput(LaunchConfigurationTabGroupViewer.java:588)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.handleLaunchConfigurationSelectionChanged(LaunchConfigurationsDialog.java:960)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog$3.selectionChanged(LaunchConfigurationsDialog.java:573)
at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:876)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:178)
at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:873)
at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1217)
at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1243)
at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:265)
at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:259)
at org.eclipse.jface.util.OpenStrategy$1$2.run(OpenStrategy.java:440)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4147)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3764)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)
at org.eclipse.jface.window.Window.open(Window.java:808)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:1154)
at org.eclipse.debug.ui.DebugUITools$2.run(DebugUITools.java:611)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:619)
at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:552)
at org.eclipse.debug.ui.actions.OpenLaunchDialogAction.run(OpenLaunchDialogAction.java:82)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:519)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:508)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)

4) Conflicting handlers for org.eclipse.ui.edit.copy: {ActionHandler(com.ibm.team.dev.launch.ui.LaunchToolbar$CopyAction@744da252)} vs {org.eclipse.ui.internal.handlers.WidgetMethodHandler@2779bd7c}

Please post questions around this workshop into the forum. Otherwise, I have run this workshop with 6.0.5, I think. The creation of the test database throws a lot of errors unfortunately, my experience is that you have to wait a looong time. Otherwise rerun the thisnk. Also consider to use the latest Java version (1.7 or 1.8) .

Also use a compatible Eclipse client.

Hello I tried to with 6.0.5, but it was installing the workshop, I got this error:

C:\RTC605Dev\downloads\WorkshopSetup-V6-20161207\WorkshopSetup>C:\IBM\CLM605\ser
ver\jre\bin\java -cp C:\RTC605Dev\downloads\RTC-Client-plainJavaLib-6.0.5/*;./*
com.ibm.js.rtcext.serversetup.ServerSetup "*****" "user" "****"
Starting Team Platform
log4j:WARN No appenders could be found for logger (com.ibm.team.repository.commo
n.internal.util.InternalTeamPlatform).
log4j:WARN Please initialize the log4j system properly.
Team Platform started
Trying to log into repository: https://localhost/ccm
Login succeeded.
Trying to find or deploy template: scrum2.process.ibm.com
Template found...
Trying to find or create Project Area: RTC Extension Workshop
Project Area found: RTC Extension Workshop
Trying to add members with roles: ScrumMaster to Project AreaRTC Extension Works
hop
Users with Roles added to RTC Extension Workshop
Found Component: RTC Extension Lab Code License
Found Component: RTC Extension Workshop Configuration - Server
Found Component: RTC Extension Lab Code - Server
RTC Extension Lab Code - Common Not found.... ,create or re-use component
RTC Extension Lab Code - Client Not found.... ,create or re-use component
RTC Extension Launches - Server Not found.... ,create or re-use component
RTC Extension Launches - Client Not found.... ,create or re-use component
Renamig Component: Test_Move_Folder Default Component to RTC Extension Launches
- Server
Rename component to: RTC Extension Launches - Server
com.ibm.team.repository.common.PermissionDeniedException: CRJAZ6053E To complete
the 'Save Component' task, you need these permissions: 'You don't have permissi
on to perform the following actions:
Modify the component name (modify/component/attributes/name)'
at com.ibm.team.repository.common.internal.marshal.util.MarshallerUtil.d
ecodeExceptions(MarshallerUtil.java:377)
at com.ibm.team.repository.common.internal.marshal.util.MarshallerUtil.d
ecodeExceptions(MarshallerUtil.java:347)
at com.ibm.team.repository.common.internal.marshal.util.MarshallerUtil.d
ecodeFault(MarshallerUtil.java:312)
at com.ibm.team.repository.transport.client.RemoteTeamService.constructE
xceptionFromFault(RemoteTeamService.java:717)
at com.ibm.team.repository.transport.client.RemoteTeamService.executeMet
hod(RemoteTeamService.java:560)
at com.ibm.team.repository.transport.client.RemoteTeamService.invoke(Rem
oteTeamService.java:202)
at com.ibm.team.repository.transport.client.ServiceInvocationHandler.inv
oke(ServiceInvocationHandler.java:43)
at com.sun.proxy.$Proxy25.renameComponent(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:90)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:508)
at com.ibm.team.repository.client.internal.ServiceInterfaceProxy.invokeS
erviceCall(ServiceInterfaceProxy.java:254)
at com.ibm.team.repository.client.internal.ServiceInterfaceProxy.invoke(
ServiceInterfaceProxy.java:110)
at com.sun.proxy.$Proxy25.renameComponent(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:90)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:508)
at com.ibm.team.scm.client.internal.ScmServiceInterfaceProxy$2.run(ScmSe
rviceInterfaceProxy.java:170)
at com.ibm.team.repository.client.internal.TeamRepository$3.run(TeamRepo
sitory.java:1355)
at com.ibm.team.repository.common.transport.CancelableCaller.call(Cancel
ableCaller.java:79)
at com.ibm.team.repository.client.internal.TeamRepository.callCancelable
Service(TeamRepository.java:1350)
at com.ibm.team.scm.client.internal.ScmClientLibraryContext.callCancelab
leService(ScmClientLibraryContext.java:71)
at com.ibm.team.scm.client.internal.ScmServiceInterfaceProxy.invokeCance
lableService(ScmServiceInterfaceProxy.java:166)
at com.ibm.team.scm.client.internal.ScmServiceInterfaceProxy.invoke(ScmS
erviceInterfaceProxy.java:94)
at com.sun.proxy.$Proxy25.renameComponent(Unknown Source)
at com.ibm.team.scm.client.internal.WorkspaceManager.renameComponent(Wor
kspaceManager.java:2415)
at com.ibm.team.scm.client.internal.WorkspaceManager.renameComponent(Wor
kspaceManager.java:2392)
at com.ibm.js.rtcext.serversetup.ServerSetup.renameOrCreateComponent(Ser
verSetup.java:780)
at com.ibm.js.rtcext.serversetup.ServerSetup.manageComponents(ServerSetu
p.java:705)
at com.ibm.js.rtcext.serversetup.ServerSetup.run(ServerSetup.java:170)
at com.ibm.js.rtcext.serversetup.ServerSetup.main(ServerSetup.java:110)

C:\RTC605Dev\downloads\WorkshopSetup-V6-20161207\WorkshopSetup>pause

Hi,
I now have to develop an RTC extension which chage the code review approve status.
You know there is a problem with this workflow. When reviewer approve the code review once, new change- set can be deliver without code review workflow.
I download all required component and install product without any problem.
IBM Rational Team Concert 6.x Extensibility document in Lab 2 i didn't see Build on State Change (new participant!) on work item save follow up action.
Where did i do wrong.
Thank you in advance.

Sorry, but the question does not make any sense to me. If you have an issue with one of the labs, I would suggest to try to repeat the lab.